Aislewright, the company

Built by retailers, for retailers

Thirty years from every side of the table.

Vendor, distributor, retailer: the people behind Aislewright have sat in all three seats, and watched good teams make decisions on incomplete data because the tools that could help cost six figures and took a year.

Vendor side, shipping in. Sell-in versus sell-through, and a relationship built on whichever of the two the other side preferred to quote.

Distribution. The middle of the chain, where inventory gets stuck and the question "whose fault is the stockout?" cannot be answered without the numbers nobody had.

Retail. Head office, store operations, finance, inside a national chain and a global one.

The engine. The first version ran across hundreds of stores for a major retailer, in production. It worked, and then it waited, because doing this properly meant running the model inside the retailer’s own building, and that was not possible at a sensible price until recently. What runs today is a ground-up rebuild: it forecasts, it orders, it explains every recommendation in a sentence, and it asks permission before it does anything on its own.

What thirty years actually buys

Building it is six weeks. Knowing what to build is thirty years.

Anyone can tell you they understand retail. Here is what understanding it looks like: the things a system has to know before the maths matters.

Master data

Your system orders in packs of 12. Your supplier changed to 6 in March.

Nobody told the system, so every order since has arrived half short. And separately the on-hand says 14 when there are 3. Shrink, a double-scanned receipt, a case on a pallet in the back. A model that assumes clean data doesn't fail loudly; it produces confident nonsense, which is worse.

Demand

A line out of stock for six weeks looks exactly like a slow seller.

Most systems read the flat line and cut the order, so it stocks out again, so they cut again, quietly strangling the line they should be growing. We know because it has happened to us. Twice.

Rhythm

Retail runs on a calendar, not a model.

The order goes to the supplier Tuesday. The DC picks Thursday. Review cycles, lead times, per-store run hours, month-end. Get the rhythm wrong and the answer arrives after the decision.

Honesty

Sometimes the right answer is "not enough data to say."

Every competitor's demo answers everything. This one is built to say "I don't have enough here to give you a credible number", and to tell you what to fix so that next week it can.

The question nobody asks to your face

"Will you still be here in two years?"

It runs in your building, which means it is not a service that can be switched off from somewhere else.

A cloud vendor going quiet takes your system with it. A box in your building does not stop working because a supplier had a bad year. That is a structural answer, not a promise.

If your team could build it

They probably can. The code is the easy part now.

Someone will offer to build you this with AI. What they cannot do is know that a line out of stock for six weeks looks exactly like a slow seller, and that every system that misses it quietly strangles the line it should be growing.

The question is whether you want your team spending the next two years discovering the exceptions we have already learned the hard way, or spending it on something only they can do. We are happy to talk about which part you are actually buying.

Your right hand in retail.

How it's built

Nothing leaves your building.

Zero open inbound ports, one database per customer, a kill switch in seconds. We publish the architecture rather than defend it on request.

Security & sovereignty →

What it costs

The shape, and the anchor.

Enterprise planning suites are six figures and take a year. Aislewright is a fraction of that, and implementation is quoted as a fixed number.

The pricing frame →

Privacy

We count visits. We don't track people.

No cookie, no third-party script. The identifier that tells one visit from another is destroyed every night.

Privacy policy →

Reach us

hello@aislewright.com

A personal reply within 24 hours, not a sequence. Security questionnaires answered directly, and in detail.

Write to us →

Integration

We read what your system already produces.

You do not need a new integration project. Aislewright works from a sales and inventory extract, the file your ERP already knows how to make. Point it at ours once, save the mapping, and it runs on a schedule.

Legacy systems, mid-market ERPs, spreadsheets, whatever is actually on the ground. We have loaded formats nobody has supported in fifteen years.

Deeper, two-way integration for Microsoft Dynamics 365 is in build. SAP and Oracle connectors follow the same pattern, but you do not have to wait for one, because the extract route works today.

Support

There is no service to be down.

Support and uptime are the same thing for a SaaS vendor and different things for us. There is no service to be down. The box is in your building, and it keeps working whether anyone answers the phone or not.

Live support 09:00–13:00 US Eastern, every US business day. Outside those hours, a four-hour response commitment, and the box keeps running regardless. That window is 15:00–19:00 in South Africa, and South African customers reach us across the working day at hello@aislewright.com.

What support is for, then, is your question, not your operation: the failure mode a cloud buyer imagines at 3am does not exist here.

Retail planning on an appliance in your building.