The shop showed stock and prices that lagged the warehouse. The import was a script on a workstation. It had no log, and no one left who would change the mapping.
What was wrong
- Customers saw availability the warehouse no longer had.
- A failure stayed quiet until orders looked wrong.
- Changing a column meant editing a script nobody wanted to open.
What was done
- Rebuilt the import as a scheduled job with the mapping written down.
- Rows that fail the rules are rejected and listed, not half-applied.
- A note on who watches the log, and how to run the job again.
What works now
- The shop follows the warehouse on the cadence that was agreed.
- A bad row is visible before it becomes a wrong product page.
- Someone other than the author can run it.
What this case is not
- No vendor name, and no uptime claim. It is a composite.
- Not a new ERP. A scheduled import with a log.
- The service behind it: Integrations.