Standing service store-keep-order-inventory-sync-healthy · revised 11 October 2026
Standing service
Check your store's orders and stock against the system they feed, every week
Each week we compare your store's orders and stock with the other system you sync to, and explain up to two causes of any difference a month, so drift is found in days, not after an oversell.
This starts a conversation by email. Nothing is charged, and nothing is monitored, until we have agreed scope and terms with you in writing.
The responsibility you hand over
A sync between a store and another system fails quietly. Notifications can be missed or arrive twice, a webhook can be deactivated, and stock written from one side can overwrite a sale made on the other. Nobody sees it until a customer is oversold or an order never ships, and then the cause is days old.
Who it’s for: Owner or operations lead of a Shopify or BigCommerce store whose orders or stock feed a fulfilment, accounting or warehouse system through a sync you control.
Usually starts when: You have fixed a sync once, or you have had a gap in orders or an oversell, and you want someone to notice the next one before a customer does.
The result: Each week the order and stock comparison for the agreed sync is done and every difference is listed; up to two separate causes a month are investigated and explained, and each month you get a written summary.
What stays true, and what we do about it
No response-time guarantee is published for this new service. A target is agreed in writing before it starts, set to what a service at this stage can actually keep.
Hours are agreed in writing before the service starts. At launch the service is not staffed round the clock, so we do not offer round-the-clock cover.
What must remain true
- The orders in your store and the orders in the connected system are compared each week, and every order on one side only or repeated is listed
- Stock for the agreed products at the agreed location is compared each week under the written rule, and every difference above the threshold is listed
- Up to two separate causes a month are investigated and end in a written explanation
What we watch
- Weekly read-only exports of order identifiers and order lines (product code and quantity, no customer data) from the store and the connected system
- Weekly stock exports for the agreed products and location from both systems
- Notices from the store platform that you forward, such as a webhook being deactivated
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| The weekly comparison shows stock differences above the agreed threshold at the agreed location. | We reconcile the sample and explain why the numbers drifted, as one of the two separate causes a month the fee covers. The correction is the separate job linked here, not part of the monthly fee. Priced as: Shopify stock out of step |
| Orders in a BigCommerce store are missing from the connected system, or a BigCommerce webhook is deactivated. | We find where the notification stopped from your exports and the notices you forward, list the orders in the gap and explain it, as one of the two separate causes a month the fee covers. The correction is the separate job linked here. Priced as: BigCommerce orders stopped syncing |
| Orders in a Shopify store are missing from the connected system. | We list the orders in the gap and explain what the exports show, as one of the two separate causes a month the fee covers. A repair is not covered by a fixed-price outcome and would be quoted separately. |
| The same order appears twice in the connected system. | We list the repeats and explain how repeated notifications are usually handled, as one of the two separate causes a month the fee covers. A change to the receiver would be quoted separately. |
| A month ends. | We send a short written summary: comparisons run, differences found and how each ended. |
We do on our own
- Read the exports you send and compare them
- Investigate differences from the exports and the notices you forward
- Write explanations and say which job would correct each cause
We ask you first
- Anything that changes your live store, the live sync, keys or permissions
- Re-activating a webhook, which you do under your own account
- Deleting or merging records in either system
- Any correction, or any work beyond the two separate causes a month, which is quoted as its own job
We escalate to you when
- The cause is outside your control, such as a vendor connector or a platform outage
- A correction would change what the sync is meant to do, not only how it does it
- More than two separate causes arrive in a month, which is more than the monthly fee covers
How you know it held. Each month you receive the comparisons run and every difference with how it ended, and the exports you sent are the evidence for each result.
How we keep it true
This service is never finished. Each month's summary shows whether orders and stock stayed in step, and it continues until you end it.
Bring Shopify stock levels back in line with the system you sync them with Job Optional
For an agreed set of products at one location, Shopify stock matches your other system under a written rule, proved on a test store and a copy of the other system, with a test sale reducing both once.
Bought separately, each time a correction is needed; not part of the monthly fee
Correcting a drifting stock sync is the job you can buy on its own.
Get BigCommerce orders flowing again to the system that stopped receiving them Job Optional
The receiving automation answers order notifications correctly under test, the webhooks are active again, and a list shows which orders missed the gap so you can catch them up.
Bought separately, each time a correction is needed; not part of the monthly fee
Correcting a deactivated order webhook is the job you can buy on its own. It covers BigCommerce only.
What is included, and what is not
- A weekly comparison result with every difference named: an order on one side only or repeated, and every stock figure that differs by more than the agreed threshold
- For each of the up to two separate causes a month, a written explanation, or a note of what only you or a vendor can change
- A written monthly summary
Included
- One sync between one Shopify or BigCommerce store and one other system, on the logic described when we agree the service
- A weekly comparison, on a day agreed in writing, of every order created since the last comparison and of stock for up to 100 agreed products at one location
- Investigation of up to two separate causes a month; differences that share one cause count as one, and each cause ends in a written explanation of what differs, the likely reason and which separate job would correct it
- A written monthly summary of the comparisons, the differences found and how each ended
Not included
- Changing your live store, the live sync or any key; those stay with you
- Correcting the cause: a corrected stock sync or a corrected BigCommerce order receiver is a separate job, bought on its own at its own price
- Repairing missing or repeated Shopify orders: we compare and explain them, but that repair is not covered by a fixed-price outcome; ask for a quote
- Paid connector apps whose internals you cannot change
- Physical stock counts and deciding the true quantity
- Out-of-hours cover or any guaranteed response time
- More than one sync or more than one stock location, unless agreed and priced
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
One order missing on one side and one stock figure beyond the threshold, planted in a copy of the first pair of exports, are both found by the first comparison
Evidence: The comparison result naming both planted differences
Each weekly comparison lists every order that is on one side only or repeated and every stock difference above the threshold, and an incomplete export is reported as unverified
Evidence: The weekly result, which you can check against your own exports
Each cause investigated (up to two a month) has a written explanation naming what differs, the evidence from the exports, and which job would correct it or what only you can change
Evidence: The written explanation attached to the weekly result
Each month's summary lists every weekly result, every difference found and how it ended, and the number of separate causes investigated (no more than two within the monthly fee)
Evidence: The written monthly summary
Sign-off. You read each weekly result and each monthly summary. An explanation counts as delivered when you accept it.
If it fails. If we cannot find a cause, we say so, explain what we looked at and what it would take, and it does not count towards the two separate causes a month. If the service is not working for you, you can end it at the end of any month.
When it fits, and when we stop
It fits when
- Your store is on Shopify or BigCommerce
- You control the sync logic or can ask the person who does to apply a change
- You can send, or schedule, read-only exports of order identifiers, order lines (product code and quantity) and stock quantities from both systems
- A person on your side reads each weekly result and decides what to do with it
- The two systems share an order and a product identifier
We stop and tell you if
- The exports cannot be produced regularly, so the comparison cannot run
- Most differences come from a system or paid connector that you cannot or will not change
- More than two separate causes a month arrive month after month, so we agree a different scope with you
- Nobody can say which system is authoritative
What could go wrong
We change nothing in your systems, so there is nothing to roll back. Ending the service leaves your sync exactly as it is, with open explanations finished or handed back.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| The comparison misses a gap because an export is incomplete | Each export carries counts and a time range, and an incomplete one is reported as unverified, never as a pass. |
| An explanation is read as proof of the true stock | Each result says it compares two exports and is not a physical count; the true quantity is yours to decide. |
| Exports contain customer data | We ask for identifiers and quantities only and tell you which columns to remove. |
Each explanation is checked by a reviewer separate from the work that produced it before it reaches you. No human supervisor is included unless your agreement names one. At launch the work is largely automated, and we say so.
Stays with a person
- You read each weekly result and decide what to do with it
- You approve any change to the live sync, keys or permissions
Access we would need
- Weekly read-only exports of order identifiers and stock, with no customer data
- A description of the sync, with secrets removed
Questions
How is this different from buying one fix?
A one-off fix corrects one drift once. This is a standing responsibility: we compare your orders and stock every week and explain up to two separate causes a month. The correction itself stays the separate job.
Do you change my live store or sync?
No. We change nothing. A correction is a separate job, proved on copies, that you apply yourself.
What if my sync is a paid connector?
We can still report differences with evidence, but we cannot change what we cannot see. The service says so plainly.
Can you repair missing Shopify orders?
We compare and explain them. A repair is not covered by a fixed-price outcome; ask for a quote.
Send an enquiry
Send us
- What the sync is, which store and platform, and what it feeds
- How the exports can be produced and how often
- Which location and which products (up to 100) matter most for stock
- Who reads the weekly results and decides what to do
- Whether there have been gaps or oversells before, and roughly when
Later, once you agree
- A weekly read-only export of order identifiers, order lines (product code and quantity, no customer data) for the same window, and stock quantities from both systems
- The agreed difference threshold (the number of units by which a stock figure may differ before it counts), the authoritative system and who to tell when something is outside your control
- A description of the sync with secrets removed; a copy of its logic and a test store only if you later buy a correction job
Your stores, the other system, the sync and all keys stay yours. We work only on exports you send, we change nothing in your live systems, and you decide what to do with each finding.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “store-keep-order-inventory-sync-healthy” as the subject.