Connecting your store to a 3PL that has no app.

If your warehouse has a ready-made app for Shopify or WooCommerce, use it. A lot of good 3PLs don't, though, and that's how stores end up with someone typing orders into a portal every morning and pasting tracking numbers back one by one.

It doesn't have to work that way. A custom sync can move orders, stock and tracking between your store and your 3PL on its own. Here's what it does, what to ask your 3PL before you start, and where these projects usually go wrong.

First, check for something ready-made.

  • Search the Shopify App Store or the WooCommerce Marketplace for your 3PL's name.
  • Ask your 3PL account manager which store platforms they connect to, and how.
  • Ask whether they connect through a shipping or order tool you already use.

If none of that turns anything up, a custom sync is the next step.

What a sync does.

Most 3PL syncs do three jobs:

  1. Orders out. When an order is paid, it goes to the warehouse with the items, quantities, shipping address and shipping method. Nobody retypes it.
  2. Tracking back. When the warehouse ships, the tracking number comes back to your store, the order is marked fulfilled, and your customer gets the shipping email.
  3. Stock back. The warehouse's counts update your store's inventory, so you don't sell what's no longer on the shelf.

Depending on the store, a sync may also handle cancellations, address changes made after checkout, and returns.

What to ask your 3PL before you start.

  • Do you have an API? Ask for the documentation and a test account.
  • If not, can you exchange files? Many smaller warehouses work with CSV files dropped on a server (SFTP) on a schedule. That works too.
  • How often do stock counts update? This decides how close to zero you can safely sell.
  • How do you handle split shipments, backorders and bundles?
  • Do your SKUs match ours? If the warehouse knows a product by a different code, the sync needs a lookup table.
  • Who do we contact when an order is rejected?

API or files: what changes.

With an API, orders reach the warehouse within moments and tracking comes back as soon as it exists.

With files, everything moves on a schedule, such as every 15 minutes or every hour. That's fine for most stores, but stock can lag behind real sales. If you sell fast-moving items, keep a small buffer so you don't oversell between updates.

Where syncs usually go wrong.

  • SKUs that don't match. One mismatched code and an order gets stuck.
  • Orders edited after they were sent. A changed address or a removed item needs to reach the warehouse too, or the old version ships.
  • Partial shipments. If an order ships in two boxes, both tracking numbers need to come back.
  • Silent failures. If the 3PL's system is down for an hour, orders have to queue and retry, and someone has to be told. A sync that drops orders quietly is worse than typing them in by hand.

A good sync keeps a log of every order it sends and every update it gets back, and it emails someone when something fails.

Want us to build it?

We handle the tech side. We build 3PL syncs for Shopify and WooCommerce stores, by API or by file exchange, with a log and failure alerts. Tell us which 3PL you use and we'll tell you what it would take.

Talk to us about a 3PL integration

Good questions.
Straight answers.

Does this work on Shopify and WooCommerce?

Yes. Both platforms have APIs for orders, fulfillment and inventory, so the sync works the same way on either.

Does it work on Shopify's Basic plan?

Yes, if it's set up the right way. Shopify limits customer names and addresses for apps created inside the store admin on the Basic plan. We build the sync as a custom app from Shopify's developer dashboard, which doesn't have that limit.

What do you need from us?

Admin access to your store, your 3PL's API documentation or file format, your product list with SKUs, and a few test orders once it's built.

What if we switch 3PLs later?

The store side of the sync stays the same. Only the warehouse side gets rewritten for the new 3PL's API or file format.

Sources