Connect Salesforce with ShipStation to sync orders, customers, and shipping details, automate label creation, and keep tracking updates consistent across teams and channels.
• Salesforce order and customer fields are mapped to ShipStation order payloads, including addresses, line items, shipping service, and requested ship dates.
• Orders are created in ShipStation from Salesforce via API-based export, with idempotency keys preventing duplicate order creation on retries.
• ShipStation shipment events (label created, shipped) are polled or received via webhook and translated into updates on Salesforce Orders/Cases, including carrier, service, tracking number, and ship timestamp.
• Status mappings normalize ShipStation shipment states to Salesforce pick/pack/ship or custom fulfillment statuses, with exceptions routed to a queue for review.
• Delta sync logic sends only new or changed orders and pulls only updated shipments since the last checkpoint to reduce processing load.
• Validation checks handle address completeness, SKU presence, and country/state formats, with errors logged back to Salesforce for traceability.
• If multiple stores or warehouses exist in ShipStation, routing rules map Salesforce channel, location, or priority fields to the correct ShipStation store/warehouse context.
.png)
We map Salesforce order, customer, and line-item fields to ShipStation and trigger shipment creation via API when an order hits the right status. This reduces manual re-entry and keeps carrier rules consistent.
Yes, we push tracking numbers, carrier, and status events from ShipStation into Salesforce records in near real time. Your support team sees the latest shipping progress without leaving Salesforce.
Typically, you send validated ship-to address, phone, email, shipping method, package notes, and item weights or dimensions when available. We also add safeguards for missing fields so shipments do not get stuck in review queues.
Yes, we can route orders to different ShipStation stores, warehouses, or carrier presets based on Salesforce fields like brand, region, or fulfillment location. This is useful for multi-entity setups and shared service teams.
Timelines depend on your order model and shipping rules, but most builds follow a short discovery, mapping, and QA cycle before go-live. scandiweb has delivered 2,100+ projects since 2003, including complex eCommerce and ops integrations.





