Automate pick-pack-ship workflows in ShipStation by pushing order data via API, triggering fulfillment, and syncing tracking back to the originating marketplace
POST new orders to the ShipStation Orders API endpoint with all required fields: orderNumber, orderDate, billTo, shipTo, items array with SKU and quantity, and orderStatus set to awaiting_shipment
Configure ShipStation automation rules in the dashboard (or via the API's automationrules endpoint) to assign orders to the correct warehouse, carrier, and service based on weight, destination, or SKU tags
Poll GET /shipments with a createDateStart filter or subscribe to ShipStation webhooks for the SHIP_NOTIFY event to receive shipment confirmation with tracking numbers
Push the tracking number and carrier code back to the originating marketplace (Shopify, Amazon, eBay) using that platform's fulfillment API to mark the order as shipped
Handle partial shipments: ShipStation may create multiple shipments for a single order; ensure your sync logic handles a one-to-many order-to-shipment relationship
Reconcile daily using the GET /shipments endpoint with a date range filter to catch any shipments created manually in the ShipStation UI that were not delivered via webhook
Known gotchas
ShipStation order numbers must be unique per store; duplicate orderNumber values will either update the existing order or be rejected depending on the configured behavior
ShipStation rate limits are enforced per API key; high-volume operations should batch order creation and implement exponential backoff on 429 responses
Webhooks are sent per store configuration; if you have multiple stores in ShipStation for different sales channels, each store requires its own webhook registration
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp