A brand signs with a provider whose rates are excellent. The integration turns out to be a nightly file, stock updates once a day, and no tracking pushed back to the store.
Customers see items in stock that sold at breakfast, nobody gets a tracking number, and the support inbox fills with the same question repeated four hundred times.
What buyers should ask
These are the questions that determine whether fulfilment works. Providers who answer them openly win the brands who know what they are doing.
1. Which platforms connect directly
Named, with whether the integration is built by the provider, the platform or a third party. Direct integrations behave differently from connectors.
2. How orders reach the warehouse
In real time or in batches, and how often. A nightly batch means an order placed at nine in the morning waits a day before anybody sees it.
3. How stock levels update
How frequently the store is told what is available. Infrequent updates cause overselling, which is the most damaging failure in ecommerce.
4. What happens when stock runs out
Whether the store is updated immediately, whether the order is held and how the brand is notified. Every brand experiences this and few ask about it beforehand.
5. How despatch and tracking flow back
Whether tracking numbers reach the platform automatically, how quickly and whether customer notifications are triggered. It removes a huge volume of customer contact.
6. Whether multiple channels are supported
A website, marketplaces, a retail channel and wholesale, all drawing on the same stock pool, which is the ground in multi channel order questions for fulfilment providers.
7. How stock is allocated between channels
Whether a brand can reserve stock for a particular channel and how conflicts are resolved. It matters enormously for brands selling in more than one place.
8. What happens with a failed sync
How errors are detected, who is alerted and how quickly. Silent failures are the worst outcome and brands should ask how they would find out.
9. What the brand can see
A portal, reporting, order status and stock movements, and whether it is live. Visibility is what a brand needs when a customer asks a question.
10. What is required from the brand
Platform access, product data, configuration and any development. Half of an integration is the brand's work and they should know before they commit.
11. How long it takes
Realistically, by platform, which connects to the sequence in warehousing enquiries from growing online brands.
12. What happens when the platform changes
Updates, version changes and whether the integration is maintained. Brands change platforms and providers should say what that involves.
13. Whether returns flow back
How a return is recorded, when stock is made available again and how the brand is told. It is usually the weakest part of any integration.
14. Publish all of this
Because brands with a technical person compare on it, and providers who publish win those conversations, which is the same clarity as how to add an AI chatbot to your Shopify store.
Getting started
Publish supported platforms, sync frequency, what flows each way and realistic timescales, then answer technical questions at any hour and connect your own systems through integrations. SpideyChat for logistics providers answers from your published pages, plans are on the pricing page, and the chatbot ROI calculator works through the numbers.