Squarespace and Ecwid Fulfillment Through a 3PL: Order Sync, Tracking Write-Back and Inventory Counts
What the connection between a Squarespace or Ecwid store and a 3PL warehouse has to do: send orders out, write tracking back and keep inventory counts in step.
Squarespace and Ecwid are popular with brands that started as a website first and a shipping operation second. Both platforms can take orders, collect payment and manage a product catalog well. Neither one picks, packs or ships. When order volume outgrows a spare room or a back office, the next step is usually a third-party logistics (3PL) warehouse, and the question becomes how the store and the warehouse talk to each other.
This guide covers what the connection between Squarespace or Ecwid and a 3PL has to do, the three data flows that matter, and what to test before you switch.
The three things the connection must do
Whatever the method, a working setup moves three kinds of data:
- Orders out to the warehouse. Each paid order needs to reach the 3PL with the ship-to address, the items and quantities, and the shipping service the customer chose.
- Tracking back to the store. Once the label prints, the tracking number and carrier have to flow back so the order is marked as shipped and the customer gets a notification.
- Inventory counts back to the store. The warehouse holds the physical stock, so its count should drive what the storefront shows as available.
If any one of these is manual, it becomes a daily task that someone eventually forgets. Missed tracking updates turn into "where is my order" emails; stale inventory turns into overselling.
How stores and 3PLs actually connect
There are three common ways the data moves, and the right one depends on the platform, your plan level and the 3PL's systems:
| Method | How it works | Watch out for |
|---|---|---|
| Direct API integration | The warehouse system reads orders and writes tracking and stock through the platform's API | API access can depend on your plan; confirm before you commit |
| Connector or middleware app | A third-party app sits between the store and the warehouse system | Another subscription, another point of failure, and its own sync schedule |
| Scheduled file feed | Orders are exported and tracking is imported on a set schedule | Delays between runs; needs monitoring when a file fails |
Squarespace offers commerce APIs for orders, inventory and products, and Ecwid offers a REST API that apps and connectors use. Whether a given 3PL plugs into those directly, through a connector, or through a feed is a per-channel question. IDCEA's approach on its ecommerce fulfillment service is the same for every platform: direct integration where the platform offers one, a scheduled order feed where it doesn't, confirmed per channel before you commit.
For a deeper look at how a warehouse system links to stores, marketplaces and carriers, see our guide to warehouse system integrations.
Getting SKUs right before anything syncs
Most integration problems are really catalog problems. The warehouse matches orders to stock by SKU, so every product and every variant in your store needs a unique SKU that matches what is on the item label in the warehouse.
Common issues on website-first stores:
- Variants without their own SKU. A shirt in five sizes needs five SKUs, not one SKU with an option field.
- Bundles defined only in the storefront. If the store sells a "starter kit," the warehouse needs to know which component SKUs make it up.
- Digital or service products mixed in. Gift cards, downloads and appointments should be excluded from the warehouse feed.
- Duplicate or reused SKUs. Retired products that share a SKU with a new one will confuse inventory counts.
Our article on SKU onboarding at a 3PL lists the item data a warehouse needs before your first inbound shipment arrives.
Order statuses and what "fulfilled" means
Both platforms track an order through a set of statuses. Ecwid, for example, separates payment status from fulfillment status, with fulfillment moving from awaiting processing to processing to shipped. Squarespace marks orders as pending or fulfilled. Decide in advance which status changes the warehouse is allowed to make:
- Should the order move to "processing" when the warehouse picks it up, or only to "shipped" when tracking exists?
- Should the customer's shipping email go out automatically when tracking is written back?
- What happens to orders you edit or cancel after they've already been sent to the warehouse?
That last point matters more than it sounds. Once an order has been released to the floor, a change in the store doesn't automatically reach the packer. Agree on a cutoff and a way to request a hold.
Inventory: which system is the source of truth
Pick one. If the warehouse count drives the store, turn off manual stock edits in the storefront, or they will be overwritten on the next sync. Set a small buffer on fast-moving SKUs so an order placed between syncs doesn't sell a unit that's already been picked for someone else. If you also sell on marketplaces, the same pooled stock should feed every channel.
A test checklist before going live
- Place a test order for a single item, a multi-item order and a variant
- Confirm each order appears in the warehouse system with the right SKUs and shipping service
- Confirm tracking writes back and the customer email sends once, not twice
- Adjust stock in the warehouse and confirm the store reflects it
- Cancel an order after it syncs and check what the warehouse sees
The short version
Squarespace and Ecwid stores can be fulfilled by a 3PL just like larger platforms; the work is in the connection, not the warehouse. Clean SKUs, a clear source of truth for inventory and an agreed order-status flow are what keep orders moving without daily manual fixes.