ShipStation integration for Amazon, Shopify and 3PL operations

This page is for 3PLs, FBA prep centers and brands that print labels in ShipStation and need it joined to Amazon, Shopify or their own warehouse system. It covers what a custom integration adds to ShipStation's own connections, the sync map from a 3PL system we built, where ShipStation fits in Amazon's inbound workflow, when the standard connector is enough, and what the API asks of the code. ShipStation, Amazon and Shopify facts link to their own documentation, checked September 25, 2026.

What does a custom ShipStation integration do?

It joins ShipStation to the parts of the operation that ShipStation does not own. ShipStation is good at what it was built for: importing orders from connected stores, comparing carrier rates, printing labels and sending tracking back. ShipStation's order management page says that once labels are created, orders move to Shipped with tracking sent back to your stores (checked September 25, 2026). A custom integration takes over where the operation has rules ShipStation cannot see: stock kept in a warehouse system, Amazon inbound shipments, per-client billing, or a channel with no ready connection.

The integration is code that runs on your accounts and calls ShipStation's API, Amazon's Selling Partner API and Shopify's APIs. It does not replace ShipStation. For most teams, the goal is to keep the label workflow packers already know and remove the copying, re-keying and double updates around it: tracking numbers pasted into Send to Amazon, orders typed into a second system, stock counts fixed by hand.

What moves between ShipStation, Amazon, Shopify and the warehouse system?

Our evidence is Pacific Prep, a full-service prep and ship company in Oregon. We built its warehouse management system, which integrates Amazon, Shopify, ScanPower and ShipStation. It runs Amazon's inbound shipment flow for FBA orders and handles non-FBA shipments with packing, item scanning and label printing. It also covers receiving, bin locations and license plates, returns and billing. The map below lists each lane of that build, what the case study records about it, and how that lane runs on today's APIs.

The Pacific Prep sync map

The case study names the flows the system runs, not the API calls behind them, so the direction and trigger in each row are our description of how that flow runs, not a quote from the case study. The fourth column maps each lane onto the APIs as they stand today, from ShipStation's, Amazon's and Shopify's documentation, and the last column is the failure we design against first. Shopify's guide About webhooks says an app can miss webhook events, that events can arrive out of order, and that apps should run reconciliation jobs that fetch data periodically (checked September 25, 2026). That is why every event-driven lane in the map also has a catch-up pull.

The screen above is the Pacific Prep inventory table: stock per client and SKU, split into total, reserved, available and quarantined units. Those counts, plus the license plate each unit sits on, hold more than ShipStation's inventory model, which tracks on hand, allocated and available units (see the API section below). In a build like this, the WMS is the one place that knows what can really ship, so it should be the one system that sends stock to the stores, and ShipStation should read stock rather than own it.

How do orders, labels and tracking flow between ShipStation and your channels?

The first decision in any ShipStation build is who owns the channel connection. If two systems both import a Shopify order, it can be picked and shipped twice. If both write tracking back, the customer can get two shipping emails, or the channel keeps whichever update arrived last. There are two sound patterns, and a build should pick one per channel and write it down.

In the first pattern, the integration listens. ShipStation's webhook subscription covers ORDER_NOTIFY, ITEM_ORDER_NOTIFY, SHIP_NOTIFY, ITEM_SHIP_NOTIFY, FULFILLMENT_SHIPPED and FULFILLMENT_REJECTED events, and can be limited to one store. The webhook payload carries only a resource URL and the event type; the integration then fetches that URL with its API credentials to get the orders or shipments (both checked September 25, 2026). ShipStation's Shopify connection says it imports Shopify orders with physical products and that tracking can flow back when you create a label (checked September 25, 2026).

In the second pattern, the integration drives. ShipStation's Create/Update Order call updates the order with a matching order key or creates a new one, and only open orders (awaiting payment, awaiting shipment or on hold) can be updated; shipped and canceled orders cannot (checked September 25, 2026). The integration should derive the order key from the channel order ID, so a retry after a timeout updates the same order instead of creating a duplicate.

Create Label for Order returns the label as a base64-encoded PDF, and the pack station prints it straight away. If a parcel ships outside ShipStation, Mark an Order as Shipped records it without a label; it notifies neither the customer nor the sales channel unless the request asks it to (checked September 25, 2026). Which node and carrier each order should use is a separate question: our guide to multi-marketplace order routing covers routing by stock, cost and each channel's ship-by date, including when an order should go to Amazon Multi-Channel Fulfillment instead of a 3PL.

How does it work with Amazon inbound and FBA?

Amazon inbound runs on Amazon's systems, not ShipStation's. The Fulfillment Inbound API (version 2024-03-20) creates inbound plans, sets packing information and generates placement and transportation options; the v0 getLabels operation, which Amazon has not deprecated, prints the box labels. API plans open in Send to Amazon once placement and transportation are confirmed. The same page says the seller must prep and label all products before sending them to Amazon's US network, and it lists the Amazon Fulfillment role for these operations (checked September 25, 2026). In the Pacific Prep build, this flow runs inside the warehouse system against Amazon's APIs; our Amazon SP-API development page covers the inbound, label and tracking work we build on them.

ShipStation enters the inbound picture in one case: small-parcel boxes shipped to Amazon on your own carrier account. Amazon's guide to shipping with a non-partnered carrier says Amazon-partnered carrier shipments are available only in the contiguous United States. With your own carrier, you pick the transportation option whose shipping mode is ground small parcel and whose shipping solution is "use your own carrier". You then confirm a delivery window for each shipment, 7 days for domestic shipments, and print Amazon's labels for each shipment (checked September 25, 2026). The carrier label on each box can come from ShipStation.

The last step is the one that gets missed. Amazon's updateShipmentTrackingDetails operation takes the tracking ID for each box, matched to the box ID from Amazon's list of inbound plan boxes, and the non-partnered carrier guide says tracking IDs must be updated for all of the boxes (checked September 25, 2026). Done by hand, that means copying one tracking number per box from ShipStation into Send to Amazon, client by client. An integration reads them from the labels and sends them to Amazon in one call per shipment.

Checklist: FBA boxes on your own carrier through ShipStation

Once the boxes arrive, the count Amazon receives has to be matched to what left your dock. When the warehouse system keeps each box's ShipStation tracking number, Amazon box ID and carton contents together, a shortfall can be traced to a single box instead of a whole shipment. That reconciliation is its own job with its own deadlines, and our page on 3PL and FBA inventory reconciliation explains how brands run it.

When is the standard ShipStation connector enough?

More often than you might expect. ShipStation's inventory management page says its tracking syncs stock levels across marketplaces and carts, and its order management page lists rules that send orders to specific warehouses, tag them, choose carriers and services, or hold them for review. Check your plan first: ShipStation's pricing page lists Inventory Sync and unlimited automation rule types on Standard and Premium, not on Starter (all checked September 25, 2026). If your operation fits those tools, switch them on and skip the build. The table below is the test we use in scoping.

Two inventory systems with ready ShipStation connectors show what "buy first" looks like. Cin7's ShipStation integration says orders from any sales channel are automatically pushed to ShipStation, and tracking flows back into Cin7. Finale Inventory's ShipStation page says Finale verifies inventory levels when orders sync from ShipStation, identifies which shipments can be sent and updates their status in ShipStation (both checked September 25, 2026). For a brand whose gap is purchasing and stock, either is likely the better choice over a custom build.

For multi-client warehouses, ShipStation's pricing page lists a 3PL manager as an add-on with its own fee (checked September 25, 2026). Ask ShipStation how it handles your rate card before you commission anything. If you are comparing full 3PL and prep-center platforms, our page for 3PLs and prep centers sets PrepBusiness, Extensiv and Packiyo against a custom build.

What does a ShipStation API integration have to handle?

Two APIs, two sets of limits and two webhook systems. ShipStation's API overview lists V2 as available with the Standard and Premium plans and says the original V1 is still supported and maintained for existing integrations. Its authentication page calls V1 legacy and says it will be removed in the future. The V2 getting-started guide says V2 is in an early release stage and that some familiar V1 features are not in V2 yet (all checked September 25, 2026).

The limits come from ShipStation's V1 requirements page and its V2 usage and rate limits page: both return 429 Too Many Requests at the limit, V1 with rate-limit headers and V2 with a Retry-After header (checked September 25, 2026). The V1 limit shapes the design. If each order takes three calls on V1, an update, a label and a webhook fetch, one key pair tops out at 2,400 requests an hour, or about 800 orders. V2's higher limit and its bulk endpoints, which ShipStation points to for creating hundreds of labels at once, move that ceiling.

Webhooks differ too. A V1 webhook carries only a resource URL and the event type, so every event costs at least one more call. ShipStation's V2 webhooks overview lists events for processed batches, tracking updates, shipments and labels created, and fulfillments shipped or rejected, with richer payloads. V2 events can be created only through the API, not in the ShipStation app, and each webhook needs a unique combination of URL, event and store (checked September 25, 2026). A build that moves to V2 should register its webhooks from code, so a new environment gets the same set.

Three more build notes. ShipStation's V2 guide says label documents are stored for a finite period, so the integration saves each label PDF on your side. The V2 shipment endpoints need create_sales_order: true for a shipment to appear on the Orders tab, and ShipStation advises building against a duplicate store connection so production is not disturbed. With one V2 key per account, rotating it means a short, planned swap, so we keep the key in one secret store rather than in several services.

The V2 inventory endpoint reports on hand, allocated and available units per SKU, warehouse and location, where available is on hand minus allocated (checked September 25, 2026). That is the field list to check before you let ShipStation show your stock. A WMS that also holds reserved, quarantined or license-plated units has to decide which of its counts maps to on hand, or ShipStation will show stock that cannot ship.

Who builds custom ShipStation integrations?

Ecomsellertool is a tech agency that builds integrations and operations software on brands' and 3PLs' own accounts. We built Pacific Prep's warehouse system, connected to Amazon inbound, Shopify and ShipStation, and prep systems for Little Owl and EzBookPrep. For a ShipStation integration, we map every lane and choose who owns each channel before writing code. We have built on Amazon's seller APIs since 2017 and shipped 50+ tools.

For brands, the order side is part of Ecomsellertool Growth OS: orders from every channel in one queue, routed to the right warehouse, 3PL or Amazon MCF, with carrier selection across 13+ carriers. If your team already prints labels in ShipStation, we connect it rather than replace it. We are not in ShipStation's partner program. What we build runs on your ShipStation, Amazon and Shopify accounts with your API keys, which your admins can revoke at any time.

You keep your accounts, your data and the custom code we build; the Growth OS base is licensed to you. If you stop working with us, your accounts, data and custom code stay with you; the Growth OS base continues under its license terms. Custom modules and AI agents are scoped in an architecture doc with a fixed price and go-live date, which you approve before work starts.

The other connections we have shipped are on the integrations hub, including the Walmart Marketplace API. To walk through your lanes with the engineers who would build them, schedule a call from the card below. If you are a brand selling on Amazon, the free 24-hour diagnostic connects through Login with Amazon, with no password shared, and reports within 24 hours of connecting, on business days. We only read data; we never change listings, prices, stock or ads.