A WooCommerce store is a WordPress site, and WordPress brings its own habits. Most fulfilment problems we see on WooCommerce are not warehouse problems at all — they are scheduling and product-structure problems on the store side.
A plugin on your site pushes orders to us and pulls tracking back. Fastest to set up, and it keeps everything inside wp-admin.
Your site's REST API is called directly, with no plugin in the middle. Fewer moving parts, slightly more setup.
We will recommend one after seeing your setup. Multi-store or high-volume installations usually go the API route; a single store on shared hosting is usually fine with the plugin.
By default, WordPress schedules background jobs against page visits. On a low-traffic store, the order push simply waits until somebody visits the site — which is exactly what you cannot afford at 2am in the customer's timezone.
wp-cron.php fixes it in minutesThis single setting accounts for most "your warehouse is slow" complaints we receive from WooCommerce stores.
We confirm all four in writing before going live, so nothing is discovered by a customer.
Plugin installed, or API keys generated with read/write scope. Either way no password changes hands.
Every variation matched to a physical SKU and location, confirmed with you in writing.
One real order through the whole chain, including the cron or webhook path you will rely on.
Enable fulfilment per product. Mixed setups with some SKUs in-house are normal.
No. Once orders are pushed, the work happens on our side. The only site-side load is the push itself and the tracking write-back.
Yes. We see the order as your store presents it; currency plugins and tax configuration remain yours to manage.
Irrelevant to fulfilment — we work at order level, not in your templates. A custom checkout that changes order meta is worth mentioning, though, because we need to know where the line items live.
Yes. Fulfilment is enabled per product, so a mixed setup is a normal configuration rather than a workaround.