Connect ShipStation to Flxpoint as a Channel to import orders from ShipStation for fulfillment and sync tracking, shipping, and carrier information back. You authenticate with a ShipStation API Key and API Secret Key generated in ShipStation under Settings, Accounts, API Settings.
What this integration does
Link Listings
Matches existing ShipStation listings to your Flxpoint products on the SKU field (configured through a Sync Listings operation)
Get Orders
Imports new orders from ShipStation that have not yet been pulled into Flxpoint for fulfillment
Sync Orders
Writes tracking, shipping, and carrier information back to ShipStation for orders that changed since the last sync
Branded labels and tracking
Flxpoint supports ShipEngine branded shipping labels and tracking portals. By passing a label image ID during the fulfillment request workflow, you can ensure generated shipping labels include your brand logo as configured in your ShipEngine or ShipStation account. Additionally, providing a theme ID allows you to utilize ShipEngine branded tracking portals, maintaining consistent customer branding throughout the post-purchase experience.
How to connect: credentials you need
Add ShipStation as a Channel, click + New Connection, and enter the values below. Then click Test Connection → Save Connection.
Field
What to enter
Connection NameRequired
A label for this connection in Flxpoint so you can identify it among your channels.
Any name you choose.
API KeyRequired
Your ShipStation API Key. In ShipStation, go to Settings → Accounts → API Settings, choose Generate API Key, then copy the API Key.
Generated in ShipStation under Settings → Accounts → API Settings.
API Secret KeyRequired
The API Secret Key shown alongside your API Key when you generate it in ShipStation. Copy it together with the API Key and paste both into Flxpoint.
Keys expire (typically 12 months) and must be rotated before expiry, or all integrations using them will fail.
Can't connect? Regenerate the API Key and Secret in ShipStation under Settings → Accounts → API Settings, and make sure your ShipStation plan includes API access: a "Payment Required" response means the plan or subscription does not currently allow API use.
Important: read before configuring
Publish Listings and Sync Listings are not supported
ShipStation does not support listing creation or product-data sync from Flxpoint, so Publish Listings and Sync Listings are unavailable. Configure a Sync Listings operation only to link existing ShipStation listings to Flxpoint by SKU, not to push product data into ShipStation.
Quantity always 0 means API V2 is not configured
On the WMS/Source side, Get Inventory returns 0 quantity for every SKU unless the connection uses an API V2 Key: a separate field from the standard API Key and Secret. ShipStation's Inventory API add-on must be enabled on your account to generate a V2 Key, and this is a Pro-level Flxpoint integration.
ShipStation API keys expire and must be rotated
ShipStation API keys have an expiry date (typically 12 months); once a key expires, every Flxpoint integration using it fails. Monitor expiry in ShipStation under Settings → Account → API Settings and update both the API Key and API Secret Key in Flxpoint before the old key expires.
Shipping Mappings are required before orders import correctly
Configuring Shipping Mappings is a required step for Get Orders. Flxpoint matches incoming ShipStation orders to shipping methods by their exact method text: if an order's shipping method doesn't match a configured mapping, the order is placed on hold. Check the shipping method text in a test order and map to it precisely.
Mapping: fields to know
Matches existing ShipStation listings to your Flxpoint products on the SKU field (configured through a Sync Listings operation)
Supported on the SKU field. Link Listings runs by configuring a Sync Listings operation on the channel: that operation must be configured for link listings to function. It matches (links) existing ShipStation listings to your Flxpoint products by SKU; it does not push product data to ShipStation.
Imports new orders from ShipStation that have not yet been pulled into Flxpoint for fulfillment
Imports new orders from ShipStation that have not yet been pulled into Flxpoint for fulfillment. Under Configure Settings: Assign User ID auto-assigns that ShipStation user to the order after import; Tag ID (numeric, visible in the ShipStation UI) restricts the import to orders carrying that tag; and Get Orders Created within the last X Days sets the import date window. Configure Shipping Mappings first so imported orders are matched to a shipping method.
Writes tracking, shipping, and carrier information back to ShipStation for orders that changed since the last sync
Syncs changes made to orders since the last sync back to the ShipStation channel: specifically order shipments: tracking, shipping, and carrier information.
Common issues
"Please confirm if the supplier received this order before attempting to re-process. Error Reason: 504 Gateway Time-out"
ShipStation's API timed out before returning a confirmation: it does not mean the order failed to reach ShipStation. Always check ShipStation first: if the order exists there, manually acknowledge the fulfillment request in Flxpoint without re-processing (re-processing would send a duplicate). If the order is not in ShipStation, it is safe to re-process. This is the most frequent ShipStation issue and happens during ShipStation API slowdowns or outages.
"429 Too Many Requests" on Send Fulfillment Requests
ShipStation's V1 API allows 40 requests per minute per API key. When multiple fulfillment-request jobs run at once or back-to-back, the limit is hit and ShipStation returns a 429. Wait briefly and re-run the job (the limit resets each minute). If it recurs, stagger scheduled job times and check whether several sources share one ShipStation API key, which compounds the exposure.
ShipStation inventory quantity always showing 0 or empty after Get Inventory runs
Quantity requires API V2. Open the ShipStation connection in Flxpoint and confirm an API V2 Key is entered in the V2 Key field (separate from the standard API Key and Secret): if it is empty, quantity defaults to 0. You must also have ShipStation's Inventory API add-on enabled before a V2 Key can be generated. This is a Pro-level integration.
Get Shipments stops returning data / tracking not flowing back
First confirm the API key has not expired (ShipStation keys are valid roughly 12 months): run Test Connection to check. If it expired, generate a new key in ShipStation under Settings → Account → API Settings and update both the API Key and API Secret Key in Flxpoint. Also verify the orders in ShipStation have a ship date and tracking number assigned: Get Shipments only imports fully processed shipments.
Orders arrive in ShipStation but Flxpoint shows "PO Pending" or won't update after shipment
"PO Pending" usually means the fulfillment request reached ShipStation but the acknowledgement back to Flxpoint failed (often the 504/429 errors above). Confirm the order exists in ShipStation, then manually acknowledge it in Flxpoint. For the reverse flow (shipped in ShipStation but not updating in Flxpoint), confirm the Get Shipments job is scheduled and running and that the shipment has a tracking number: trackingless shipments are not picked up.
"Payment Required" or "ShipStation API not working" error on connection
A Payment Required response usually means the ShipStation subscription is lapsed or suspended, or the plan does not include API access. Log into ShipStation directly to confirm account status and that API access is part of your plan. This is separate from an expired key: it is a billing/plan issue that must be resolved in ShipStation before Flxpoint can reconnect.
FAQs
What is the difference between ShipStation as a Channel and ShipStation as a WMS/Source?
ShipStation as a Channel imports orders from ShipStation into Flxpoint and syncs tracking back: use it when ShipStation is your order source and Flxpoint handles downstream fulfillment. ShipStation as a WMS/Shipping Source (configured under Sources) sends fulfillment requests from Flxpoint to ShipStation for label purchase and warehouse processing, then pulls shipment tracking back: use it when ShipStation is your warehouse/3PL and Flxpoint is your order hub. Many users run both at once.
My orders are not importing from ShipStation. What should I check?
Two common causes. First, the order status: Flxpoint only imports orders whose status matches your Get Orders configuration; a non-matching status is skipped. Second, the date range: increase the "Get Orders Created within the last X Days" value if the expected orders are older than the configured window. Also confirm the Tag ID setting: if a Tag ID is specified, only orders carrying that tag import.
Can I direct orders to a specific store within ShipStation?
Yes: the Send Fulfillment Requests mapping template includes an optional Store ID field. Map a fixed or field-based Store ID value to route orders to a specific store in your ShipStation account. If you don't need to differentiate stores, leave it as "Don't Map." The Store ID is numeric and visible in your ShipStation account settings.
How do I handle ShipStation orders fulfilled without a tracking number?
When ShipStation ships an order without a tracking number (for example, USPS First Class without tracking), the Get Shipments job won't pick it up and the order stays open in Flxpoint. These must be manually marked fulfilled in Flxpoint and the channel updated separately. Consider setting a placeholder tracking value in ShipStation for trackingless shipments, or use Flxpoint order automation rules to handle these cases.
Does cancelling a shipment in ShipStation automatically update Flxpoint?
No: cancelling or voiding a shipment in ShipStation does not automatically update the order status in Flxpoint. Flxpoint reads shipment data via Get Shipments and does not poll for cancellations. If a shipment is cancelled after it was already imported into Flxpoint, the order stays in a fulfilled/processed state and must be corrected manually.
