• Import the Petra Industries catalog with core details (title, description, categories, images).
• Update pricing and cost when available to your account.
• Keep on-hand quantities current and archive items that are no longer available.

• 1Select Connection — Choose your Petra Industries connection.
• 2Retrieve Catalog — Flxpoint retrieves the Petra Industries product data — products, attributes, pricing, inventory, and images.
• 3Map Fields — Incoming data is matched to your Mapping Template.
• 4Persist — Values are saved to the Global Inventory Pool and flow to channels after your next push.

• 1Connect an Integration — Choose Petra Industries and select your existing connection.
• 2Configure Settings — Optionally enable Archive/Un-Archive Inventory so SKUs missing from the feed are archived and auto-restored when they reappear.
• 3Define a Mapping Template — Start with the recommended fields below and adjust as needed.
• 4Save & Schedule — Run manually first to verify, then enable a daily schedule (jobs run in UTC).

• Catalog not importing: Open the Petra Industries connection and click Test Connection. If it fails, re-enter your credentials and retry.
• Items missing: Confirm your Petra Industries account is approved to access those products and that they are present in the feed your account receives.
• Quantities look stale: Confirm the job ran successfully on its schedule and did not error before completing.

• Submit one dropship order to Petra Industries per eligible Fulfillment Request.
• Pass the customer's shipping address and ordered line items.
• Mark the order as sent once Petra Industries accepts it.

• 1Connect an Integration — Choose Petra Industries and select your existing connection. Click Test Connection, then Save and Proceed.
• 2Configure Settings — Set any order-level options your workflow requires (for example, a review hold).
• 3Select a Mapping Template — Choose the default Petra Industries template or create your own.
• 4Save & Schedule — Test with a single order first to verify Ship To mapping and connectivity, then enable automation across your routing group (jobs run in UTC).

Map your Flxpoint Fulfillment Request fields to the Petra Industries order so dropship orders submit cleanly.

• Order rejected for missing fields: Audit your mapping template to ensure every required field is mapped and supplies a non-empty value.
• Duplicate PO error: If you need to retry an order, change the FR/PO reference and resend.
• Order failed with a connection error: Click Test Connection on the Petra Industries connection. If it fails, re-enter your credentials and retry.

• Identify Petra Industries orders shipped within the configured window.
• Update orders with tracking number, shipping method, and ship date.
• Associate shipped items by SKU and support partial shipments.

• 1Connect an Integration — Choose Petra Industries and select your existing connection.
• 2Configure Settings — Set Fetch Shipments for Days (how many days back to look). Most teams use a 10- or 15-day window.
• 3Define a Mapping Template — Use the recommended fields below.
• 4Save & Schedule — Run on demand or schedule periodic runs (UTC) — for example, every 2 hours — to keep tracking current.

Fields are split between header level (one per shipment) and item level (one per shipped line).

• How far back should I fetch? Most teams use a 10- or 15-day window. Increase it if you expect late confirmations.
• Does the PO number have to match the case exactly? No. Shipment lookup by PO number is now case-insensitive, so a shipment is found regardless of whether the PO is entered in uppercase, lowercase, or mixed case.
• Can partial shipments import? Yes. Each Petra Industries shipment attaches to the original order with its own items and quantities.

• "No data" responses: The order may not have shipped yet. Confirm shipment status with Petra Industries and re-run after the shipment is dispatched.
• Shipment not found for a PO number: Previously, fetching shipment data could fail if the PO number's letter case didn't match what Petra Industries stored (for example, a lowercase PO searched against an uppercase value such as ebyus05-14589-57987 vs. EBYUS05-14589-57987). This is now resolved — shipment lookup by PO number is case-insensitive, so the shipment is found regardless of how the PO is typed. No additional action is required to benefit from this fix.
• Tracking not linking to the order: Confirm the shipment's PO/Reference matches your original Fulfillment Request Number. With the case-insensitive lookup above, differences in letter case no longer prevent a match.
• Authentication errors: If the run fails with an auth error, click Test Connection on the Petra Industries connection and re-enter your credentials if needed.