Reference

The operations
reference

These pages answer the questions that arrive before a platform decision and usually get taken after it: which system holds stock truth, which one owns the order promise, where the ledger takes its numbers from, and how any of it connects.

Vendor-neutral throughout, and that is a position rather than a hedge — no vendor can write the page that compares their competitors, which is why these are worth reading and their brochures are not.

What is not written yet

Every page above stops at the same line, and it is the same line for all of them: the per-vendor rows. Which product genuinely holds committed stock per location, which connector survives a channel going down mid-sync, what each arrangement costs to run rather than to licence.

We have not implemented across that field at this merchant size. A feature grid assembled from vendor datasheets is indistinguishable, to a reader, from one built out of implementations — and only one of them is worth anything. Those rows appear named, dated and attributed as real implementations produce them.

The diagnostic is the version of this that does not need a case study: which system is nominated to be right today, where the order promise is made, and which reconciliations are already being done by a person.

Book the diagnostic

Tell us what is breaking

What the systems are doing now, and what you need them to do. We will tell you whether it is a platform problem or something cheaper.