Petra Industries as a Source

July 17, 2026

Summary

Petra Industries is a wholesale distributor of consumer electronics and accessories, and a pre-built electronics integration in Flxpoint. One FTP connection (Connection Name, FTP Protocol, Host, Port, User, and Password) is reused by every operation. The integration runs Get Inventory (Primary and Secondary), Send Fulfillment Requests, and Get Shipments. Get Shipments uses a configurable Fetch Shipments for Days window (10–15 days recommended) with case-insensitive PO lookup and support for partial shipments; Send FR requires a complete ship-to address plus SKU and Quantity, with the FR Number sent as the PO reference. For operation-level mapping guidance contact support@flxpoint.com.

What this integration does

Get Inventory (GIP)

Imports the full Petra catalog daily — products, pricing, and quantity.

Get Inventory (GI-S)

Refreshes pricing and quantity for known SKUs between full GIP catalog runs.

Send Fulfillment Requests

Sends orders (Fulfillment Requests) to Petra.

Get Shipments

Pulls Petra tracking numbers and ship dates back into Flxpoint.

How to connect - credentials you need

Petra Industries uses a single connection type for all operations. Add a Petra Industries source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection.

Connection NameRequired

A label to identify this connection in Flxpoint. Choose any descriptive name.

FTP ProtocolRequired

The FTP protocol to use (FTP or FTPS), as provided by Petra Industries.

FTP HostRequired

Your account-specific Petra Industries FTP server hostname.

FTP PortRequired

The FTP port for the connection, as provided by Petra Industries.

FTP UserRequired

Your Petra Industries FTP username.

FTP PasswordRequired

Your Petra Industries FTP password.

If Test Connection fails, re-enter your Connection Name, FTP Host, FTP Port, FTP User, and FTP Password carefully and check for trailing spaces. For extended operation setup and field mapping beyond connection, contact support@flxpoint.com.

Important - read before configuring

One connection covers all operations — FTP credentials from Petra Industries

A single Petra Industries connection (Connection Name, FTP Protocol, FTP Host, FTP Port, FTP User, FTP Password) is reused by GIP, Send FR, and Get Shipments. You do not need separate connections per operation. Credentials are provided by Petra Industries. If Test Connection fails, re-enter credentials carefully and check for trailing spaces.

GIP field mapping: SKU (required), Title (required), Cost = Dealer Price (required), Quantity (required)

GIP imports: SKU (required), Title (Product Name), Cost (Dealer Price — USD), MSRP, MAP, Quantity, UPC, Image URLs. The Parent SKU maps from Product Line to link variants to parent products. Run GIP daily for a full catalog refresh. Enable Archive/Un-Archive in GIP settings to automatically zero out and later reactivate items absent from the feed.

Send FR required fields: FR Number, Ship To Name + Address + City + State + ZIP + SKU + Quantity

Send FR sends the Fulfillment Request Number as the Petra Industries PO/Reference. Required fields: FR Number, Ship To Name, Address Line 1, City, State, ZIP, SKU, Quantity. Orders missing any required field may be rejected. For duplicate PO errors, change the FR/PO reference and retry. Test with a single order before enabling automation across your routing group.

Get Shipments: Fetch Shipments for Days window (10–15 days) + case-insensitive PO lookup + partial shipments

Get Shipments uses a Fetch Shipments for Days setting — 10 or 15 days is recommended. Increase it if you expect late confirmations. PO number lookup is now case-insensitive — a previously common issue where lowercase POs (e.g., ebyus05-14589) didn't match uppercase Petra records is now resolved. Partial shipments are supported; each shipment attaches separately with its own items and quantities. Schedule every 2 hours for prompt tracking.

Operations - fields to know

Get Inventory (GIP)Get Inventory (GIS)Send Fulfillment RequestsGet Shipments

Field mapping for this operation is configured with Flxpoint Support.

Get Inventory (Secondary) reads a delimited feed whose columns depend on your Petra Industries feed setup, so field mapping for this operation is configured with Flxpoint Support.

Source Field	Maps To (Petra Industries) — Notes
Fulfillment Request Number	→ PO Number / Order Reference. Required. Sent to Petra Industries as the PO/Order Reference — must be unique per submission; retrying a failed order requires a new FR/PO reference.
Fulfillment Request line → SKU	→ Petra SKU. Required. Sent per line item.
Fulfillment Request line → Quantity	→ Order Quantity. Required. Units ordered for the line.
Ship To Name	→ Ship To Name. Required. Capped at 25 characters — longer names are rejected.
Ship To Address Line 1 / Line 2	→ Ship To Address. Required (Line 1). Each line capped at 25 characters.
Ship To City / State / Zip	→ Ship To City, State, Zip. Required. City capped at 20 characters.
Ship To Phone	→ Ship To Phone. Contact phone number for the shipment.
Source Shipping Method	→ Ship Via Code. The shipping method/carrier code sent to Petra Industries for the order.
UPC	→ UPC Code. Product UPC, when mapped.

Field	Maps To — Notes
TrackingNum	→ Shipment → Tracking Number. Required. Petra Industries package tracking number.
ShipViaCode	→ Shipment → Ship Method. Carrier/ship method code returned by Petra Industries.
PO Number	→ Shipment lookup key. Matched against your Fulfillment Request/PO Number — the match is case-insensitive.
Item SKU	→ Shipment Item → SKU. Required. Associates the shipped line to your catalog.
Item Shipped Quantity	→ Shipment Item → Quantity. Required. Actual units shipped for the line — not copied from the original order quantity.
Shipping Cost	→ Shipment → Shipping Cost. Freight/shipping cost reported by Petra Industries, when available.

Common issues

Send FR rejected — missing required fields or duplicate PO reference

Most Send FR rejections are caused by: (1) missing required fields — audit your mapping template for Ship To Name, Address Line 1, City, State, ZIP, SKU, and Quantity; all must be mapped and supply non-empty values; (2) duplicate PO reference — if retrying a failed order, you must change the FR/PO Reference before resubmitting; (3) connection error — if the job errors, click Test Connection on the Petra Industries connection and re-enter credentials if needed before resubmitting with a new FR/PO reference.

Get Shipments returning no data or shipment not found for a PO

If Get Shipments returns no data: (1) confirm the order has actually shipped on Petra Industries' side — "No Data" is expected for unshipped orders; (2) check whether the order shipped outside the configured Fetch Shipments for Days window — increase the window if needed; (3) confirm Tracking Number and SKU + Quantity Shipped are mapped in the template — unmapped required fields prevent shipment data from importing; (4) PO case mismatch was a known issue but is now resolved — case-insensitive lookup means uppercase/lowercase differences no longer block matches.

FAQs

What fields does Get Shipments return from Petra Industries?▸

Get Shipments retrieves header-level and item-level shipment data. Header fields: Tracking Number (required), Shipped At, Shipping Method, PO Number / Order Reference. Item fields: SKU (required), Quantity Shipped (required — actual units shipped per line, not copied from the PO). Partial shipments are supported; multiple shipments can attach to one order. The case-insensitive PO lookup fix means differences in letter case (e.g., uppercase vs lowercase) no longer prevent a shipment from being found.

What happens if items are missing from a GIP run?▸

Two things to check if items are missing: (1) confirm your Petra Industries account is approved to access those products — some items require account-level authorization; (2) if Archive/Un-Archive is enabled, items absent from the latest feed are archived (qty set to 0) until they return. Stale quantities usually indicate the job errored before completing — check the job log, fix any connection issues, and re-run. For items that genuinely shouldn't be in your catalog, the archive behavior is working as intended.

Back to Electronics