Skip to content
EazyShop

Contents · 21 sections

EazyShop · commerce platform

Most platforms end at the checkout.

Then the order still has to be picked, packed and handed over. One system for both halves — running alongside the till and the back office you already have.

One shop or a chain. Trade accounts or shoppers. Same system, configured.

A dark surface, a phone, and a line of warm light leaving its screen — the beginning of an order.
  1. Ordered
  2. most stop here →Picked
  3. Packed
  4. Handed over

01 · The shop

What your customers actually touch

A shop that answers every question — what is listed, what it costs, whether it can be had today — for the branch or the trade account in front of it, and gives the same answer on the tile, in the basket and at the checkout. The whole shop on every screen it is opened on, rather than a desktop site that shrinks.

A shop being used on a phone: a grid of product tiles, a thumb scrolling, one tile opening into a product, and the basket counter lighting up.
  • Upright panels of different sizes standing in a rack, one forward and picked out.

    Real pages, not filtered lists

    Departments, brands, origins and collections each get their own page, artwork and editorial copy — the pages that earn search traffic instead of a query string that never ranks.

  • A magnifying glass through which mismatched shapes emerge as identical aligned blocks.

    Search that survives how people type

    A typo, a plural, a part number, a description instead of a name, a second language, or a barcode scanned while standing in the aisle.

  • One block with price tags hanging from it at the same height.

    One answer, everywhere it is asked

    Price and availability resolved for the shopper's branch or their signed-in account, and the tile, the basket and the checkout read the same calculation — so they cannot say three different things.

  • A phone with one app tile lifting off its screen onto a shelf beside it.

    It installs without an app store

    To the home screen of a phone or a desktop, running full screen without browser furniture, with notifications about their own order. No app store, no download, no second thing to maintain.

  • A phone with a key rising out of its screen — no lock, no password.

    A number and a code

    Signing in is a phone number, with saved addresses, saved cards and order history behind it. No password to forget at the moment of paying.

  • A basket of goods with a list standing behind it and an arrow curving back down into it.

    Named lists, kept across their devices

    Several lists they name themselves, on every device they sign in from, and everything they have bought before ready to repeat — with anything unavailable in their branch filtered out before they see it.

  • A van with a dashed route running out behind it to a single door.

    Tracking on a link, with no login

    The stage, the promised time, the round on a map while the van is out, and proof of delivery at the end. The customer who is chasing an order is the last person who should meet a password prompt.

  • Two goods joined by a bracket with a third hovering above as the suggestion.

    Suggestions that can say why

    Often bought together, back in your branch, bought before — learned from real baskets, so a new shop recommends properly on the day it opens rather than after six weeks of traffic.

  • Three identical plates fanned out at different angles from one point.

    In the language they think in

    The whole shop, including everything your own team wrote, with clean per-language addresses. A missing translation falls back field by field rather than breaking the page.

A lens through which found items land on a shelf, while the ones that found nothing drop into a tray that keeps them.

02

Search

Every search that finds nothing is kept as demand you could not meet, so the search box doubles as a buying list.

One product with four price tags hanging at different heights, and a dial below selecting which one applies.

03

Price

One product carries several correct prices at the same time — per branch, per trade account, per quantity bracket — each able to start and stop on its own date. Which one applies is decided in one place, so the shelf, the basket and the invoice cannot differ.

04 · Trade accounts

Selling to businesses is not a discount

A trade buyer is a different shape of customer: the price depends on who is asking, the unit is a case, the payment is on terms, and the whole thing is bought by a person with a purchase order to satisfy. All of it is the ordinary path here rather than a module bolted to a consumer shop.

A pallet of sealed cases beside a single loose carton — the same goods, priced as different things.
  • A price tag fixed to one account card by a rigid arm with a closed clasp.

    The price depends on who is asking

    Every price the shop shows is resolved for the signed-in account, never a list price with a discount applied afterwards. The account is taken from the session rather than the request, so an account cannot be made to quote somebody else's contract.

  • A case, a pack and a single item of the same goods, each with its own separate tag.

    Case, pack and each are different things

    Each carries its own price and its own multiplier back to the base unit. A case price is a price, not an item price multiplied up — which is the bug wholesalers reject a platform for.

  • A descending staircase with larger stacks of goods on each lower step.

    Quantity breaks, priced properly

    The price for one and the price for forty are separate answers to a separate question, asked per account and per quantity — built in rather than approximated with a promotion rule.

  • An open ledger with a pen on it, and a card terminal turned face down and pushed aside.

    No card at the end

    The trade checkout has no payment step: the order is placed against the account and settled on its terms. The same engine runs a full card checkout for shoppers — both commercial models ship, so the checkout is not wired to one kind of buyer.

  • A carton travelling with a docket clipped firmly to its side.

    Their purchase order travels with it

    The buyer types their own PO number and it stays on the order through fulfilment and onto the confirmation. A buyer who cannot put their PO on an order cannot get your invoice through their own accounts department.

  • An open shelf of goods with a gate lowered in front of the price tags beneath them.

    Catalogue open, prices behind the login

    Product pages render for search engines while price, stock and ordering wait for an authenticated account — the standard shape of a trade site, out of the same components as the consumer one.

  • A list with an arrow curving from it back down into a crate already holding goods.

    Their own history is the order form

    Last ordered, how many, one tap — across hundreds of lines at once, with anything unavailable filtered out first. Trade buying is replenishment, not discovery.

  • A folder with documents fanned out of it and three stepping plates leading away, the last raised.

    Opening an account is a process, not a form

    A public application captures the business, its type and size, its addresses and its documents, then moves through your own status vocabulary with a written reason required to reject or hand off — and matches itself back to the customer record it becomes once real orders appear.

  • A figure beside a desk with lines running out to two buildings.

    Reps are a role, not a spreadsheet

    A scoped login each, the account's money position and whole conversation in one place, and an assigned rep on accounts, applications and enquiries — kept deliberately distinct from whoever originated the lead and whoever typed the record in.

Blank records lifting out of a filing tray and gaining a tag and a picture as they rise.

05

Catalogue

Read from wherever your products already live — a till system, an ERP, a database, a feed — with detail and pictures generated where you have none.

One item linked out to four systems that each call it something different, with a correction laid over the supplied record rather than erasing it.

06

Product information

A PIM inside the platform rather than a second system bought and integrated. One identity per item however many names your other systems have for it, and your team's corrections layered over supplied data so the next import cannot undo them.

07 · Page builder

No page you cannot build

The reason a marketing team stops raising tickets. Pages are assembled from ready sections by the person who wanted them, previewed at real widths, and published when they say so — with the previous version kept every single time.

A shop page assembling itself on one screen: a banner, a row of product tiles and an editorial block settling into place, and a hand lifting one section to move it.
  • A hand lifting one panel clear of a stack that has opened a gap for it.

    A visual editor, not a form

    Drag to reorder, edit in place, and preview at phone, tablet and desktop widths before anyone else sees it.

  • Panels of different proportions fanned out in a loose stack.

    Sections for what a shop actually needs

    Banners and heroes, product rails, editorial and text, video, galleries and collages, FAQ, testimonials, comparison columns, tabs, maps, calls to action, competitions and forms.

  • An open tray with assorted goods falling into it.

    Sections that fill themselves

    Price cuts, new arrivals, best sellers, a shopper's own repeat purchases — pulled live from the catalogue, and freezable into a hand-picked list the moment you want control instead.

  • A panel with a hatch open in its face and a block being fitted into the slot behind it.

    Your own HTML where nothing fits

    Drop in your own markup and it renders, versions and schedules like every other section. The escape hatch is part of the product rather than a favour.

  • A panel with a dial on its face and a gate arm raised beside it.

    Scheduled and targeted, per section

    Start and end times and which branches see it, decided on the server — so a local offer never reaches the rest of the chain, and a promotion takes itself down at midnight.

  • Stacked plates with an arrow lifting one back out of the stack.

    Every save keeps the last version

    And restoring is not destructive: putting an old version back saves the current one first, so you can undo the undo. Nobody has to be brave to try something.

  • Two differently shaped buildings, both built from the same repeated blocks.

    Your corporate site, from the same parts

    About, contact, policies, FAQ and editorial pages built the same way. One site, one login, one place to change a phone number.

  • A mechanical arm reaching through a gate to place a panel on a stack.

    Your AI agent can build pages too

    Connect the assistant your team already uses and describe the page. It works through an approval you grant and revoke from your own login, every edit is a restorable version, and nothing goes live until a person publishes it.

  • A stack of panels with a dashed empty gap and one new panel hovering above it.

    A section that does not exist yet

    Is not a quarter. Tell us what the shop needs and it is a small contained change — which is why there is no number of section types on this page. Writing your own is what we are building next.

Assorted goods passing under a gate; one comes out with a tag clipped to it.

08

Promotions

Automatic offers that apply themselves and coupon codes customers type — percentage, amount, free delivery, buy-X-get-Y — each with a budget, a cap and one rule for what combines. Reduced prices can also arrive ready-made from your till, your ERP or a supplier feed, dated to start on their own.

Panels suspended at different heights, each casting a measured footprint on the ground.

09

Marketing

Pop-ups, takeovers, banners and exit offers, targeted and capped, measured in baskets rather than opens.

10 · Customers

A segment that changes the shop, not just the mailing

Customers, orders, messages and campaigns sit in one system, so a group defined once is read by the storefront and the campaign alike. That is the difference between personalising a subject line and personalising a shop.

People gathered into groups of different sizes, a few linked back to a record.
  • Six different threads arriving into one panel.

    The whole relationship on one screen

    Sign-ins, what they looked at, what they searched for, baskets, orders, payments, messages and how they answered a campaign — so whoever picks up the phone is not reading three systems.

  • One group of people with two lines leaving it — one to a shop, one to a message.

    One definition, two readers

    A segment is defined once and both the shop and the marketing tool read the same one. There is no export, no nightly sync, and no chance of a customer being in the group for the email and out of it for the offer.

  • Two shelves holding the same goods arranged in a different order, each with a different leader.

    Merchandising per audience

    Featured ranges and the arrangement of the categories themselves served differently to different groups — without running a second site or maintaining a second catalogue.

  • Stepping plates at descending heights with a figure standing on the second.

    Lifecycle worked out, not maintained

    New, active, at risk, lapsed — computed from what people actually do, so nobody has to keep a list up to date and the definition cannot quietly drift between teams.

  • A shopping basket on a balance scale, with an envelope discarded beside it.

    Campaigns measured in baskets

    Pop-ups, takeovers, bars, slide-ins, banners and exit offers, each targeted, capped and scheduled — and counted against the orders that followed rather than the emails that opened.

  • One message leaving by three chutes to three different receivers.

    Email, text, messenger and push

    Order messages and marketing from templates your own team edits, in the languages the shop runs in — to an inbox, a phone number, a messenger or the device itself, without a separate tool holding half your customer data.

  • Five differently shaped notes falling into one tray with an owner tag on its edge.

    Every enquiry in one queue

    Contact, feedback, trade and supplier applications, competition entries and requests for a call — each with an owner and a status, rather than four inboxes and a shared mailbox nobody reads on Fridays.

  • A card with six impressions, four of them filled, and a stamp beside it.

    Loyalty and referrals

    Points, tiers and the customers who brought other customers, tied to the same account record the orders hang off.

  • One drum with two arms reaching into it — one from a shop, one from a desk.

    One place the answer comes from

    Because it is the same database as the orders, a question about a group of customers is a query rather than an export, a spreadsheet and a week.

11 · After the order

The half that runs beside what you already have

An order still has to be picked, packed and handed over — and none of that asks the system that already owns the order to change. Every order is mirrored into a state machine of its own with a full event log, while the checkout goes on straight through to the system of record.

Two cabinets side by side: the left one closed and sealed, the right one open and working, with a single arrow running from the sealed one to the open one and never back, and a crate leaving on a conveyor toward a van.
  • Two identical closed cabinets joined by one arrow that points from the left to the right and does not return.

    It never writes back to your system of record

    Your existing system keeps owning the order. This one mirrors it and runs the warehouse from the mirror, alongside — the checkout a customer sees cannot be affected by it, and switching the whole thing off leaves your record exactly as it was. Every other platform asks to be your order system. This one is built not to be.

  • A row of four identical cartons with the leftmost drawn forward out of the line by a hook, the rest left standing.

    Picked by expiry, not by what is nearest

    Stock is reserved earliest-expiry-first, against a minimum remaining shelf life you set, so the lot that has to move is the lot that moves. A storefront that treats stock as one number cannot do this, and for anything perishable it is not a refinement.

  • One continuous folded path threading between shelf blocks from one corner to the opposite one, with totes standing on it.

    Many orders, one walk

    Orders batch into a single list routed through the zones in walking order, with a full-screen card that stops the picker at each change of area. Every line stays bound to the order it belongs to — batching that loses the binding is how a round ends with the right goods and the wrong customers.

  • A scanner on a stand aimed at a boxed item, its beam stopping at the box's face, with a gate beside it still open.

    The scan checks the pick, it does not make it

    A camera or a handheld scanner classifies what was found — the right item, the wrong item — and shows the picker. It never commits the line on their behalf. A scanner that silently accepts is a scanner that silently ships the wrong thing.

  • A weighing platform with an irregular wrapped parcel on it and a blank upright face at the back edge.

    Weighed where it is picked

    Anything sold by weight is weighed at the shelf, in pounds, kilos or ounces, and that weight travels with the line to the invoice. Not an estimate corrected afterwards by somebody reading a printout.

  • An open envelope standing upright with a sand timer leaning against it, most of the sand already fallen.

    The customer is asked, and the question expires

    A shortage or a replacement becomes a question put to the customer with a deadline on it, and the deadline is enforced rather than hoped for. An approval that waits forever is a van that waits forever.

  • One open crate with three sealed parcels of different sizes lifted out and set in a row beside it, each with its own tag.

    The charge follows the parcel

    One order can leave as several parcels, each with its own packaging, its own lines and its own real weight — including a line packed short. What went in the box is what is charged for.

  • A kerbside stand with a sealed parcel at its foot and a painted bay marking on the ground beneath.

    Collection is a link, not a login

    The customer gets a link and uses it: on the way, with an arrival time and the vehicle; then arrived, with the bay they are parked in. At a desk inside or at the kerb. Somebody collecting an order is the last person who should meet a password prompt.

  • A delivery van with a single map pin standing on a stem directly above its roof.

    Tracking that stops sharing when it should

    The stage, the timeline, the van on a map while it is genuinely out, and proof of delivery at the end — a photograph, a signature and where it was left. The driver's position is exposed for that delivery and not a minute before or after it.

Five lines arriving from five directions and merging into one channel.

12

Orders

Web, phone, a rep, a file or a partner — one path, and the same order arriving twice is still one order.

A warehouse aisle with one route threaded between the racks to a marked bay.

13

Picking

Many orders for one location filled in a single walk, every line still bound to the order it belongs to.

An open carton with items placed inside and a docket resting on the bench beside it.

14

Packing

Declare what actually goes in the parcel. The charge follows the packed order, not the ordered one.

Ground divided into zones with raised edges, a van standing on one and a route crossing two.

15

Delivery

Zones drawn on a map, slots that close when the round is full, your own vans or a carrier.

A counter with a hatch, parcels queued behind it and a marked bay on the ground in front.

16

Collection

A pickup desk with a live queue, the kerb with the customer's arrival and plate, and a kitchen screen.

One carton with three separate chutes leaving it — back to the rack, to the bin, to holding.

17

Substitutions and returns

When something is not on the shelf the picker sees the customer's own instruction and a ranked replacement — or, on a trade account, it becomes a backorder held against that line rather than a silently short delivery. When goods come back: requested, approved, received, then decided line by line — onto the shelf, scrapped or held — and the money restated on what was actually supplied.

A panel with bars above it and two blank ribbons standing for written conclusions.

18

Reporting

A dashboard that writes the conclusion, not only the chart.

A machine drawing a card up from a drawer of records, with a kept copy of the previous version beside it.

19

AI analyst

Ask in plain English which lines slipped and where the growth came from. It answers from live data and cannot state a figure it did not just fetch.

An arm reaching in from outside through a marked gate to lift one panel from a stack, with the versions already kept standing apart beside it.

20

MCP

Point your own AI agent at the shop and give it ordinary instructions. It edits pages, copy and products under permissions you grant and revoke, and every change it makes is a version you can restore.

21 · Your other systems

Nothing you run has to be switched off

This is not a migration in the sense that word usually carries. Your tills keep ringing, your back office keeps invoicing, your reporting keeps reporting. The platform reads what they already produce, tells them what it has done, and can go live on one branch or one part of the range before it goes live on everything.

Four existing machines, untouched on their own tiles, with one new rail threading between them.
  • A reading arm resting on a drum with a ribbon of records leaving it.

    It reads the files you already produce

    Your item file and your price file, in the form they already come in. Nothing is retyped, nothing is re-keyed into a second system, and no team is asked to maintain the catalogue twice.

  • An irregular block beside a socket moulded to exactly that profile.

    The importer takes the shape of your source

    It builds itself from the structure it is given rather than demanding a template, so the field your till vendor adds next year is a configuration change here instead of a project.

  • One block sending small parcels outward along three arcs.

    It tells your other systems what happened

    An order placed, a price changed, a customer created — sent to whatever you want told, so the accounting system and the warehouse hear it from one place rather than from four nightly jobs.

  • A plug in a socket with the lever beside it raised.

    Connections you grant and withdraw

    Each one is registered by you, scoped to what it needs, and revocable in seconds. Nothing has standing access because somebody set it up once and left.

  • A drum with one pipe to a separate panel, and a key hanging on the pipe.

    Your analysts connect to the data directly

    A curated, business-named, read-only feed your reporting tool talks to with a key you issue — rather than an export somebody schedules and a spreadsheet that is wrong by Tuesday.

  • A panel with four differently shaped sockets, one filled by a matching plug.

    Payments, messaging and delivery are sockets

    The gateway, the email and text provider, the carriers and the third-party logistics you already use plug in. Changing one later is changing one, not rebuilding a checkout.

  • A grid of nine tiles with exactly one raised and picked out.

    Start with one branch or one range

    The platform does not require a cutover weekend to be worth anything. Run it beside what you have, on a part of the business, and widen it when it has earned that.

  • A wall of blocks with one drawn part way out, the wall intact around it.

    Replaceable a component at a time

    Because the parts talk over interfaces rather than being welded together, one of them can be swapped without the rest noticing — including, eventually, ours.

  • A drum with an open padlock hanging on it and no chain anywhere.

    Your data stays yours

    Your catalogue, your customers and your orders, in your infrastructure, exportable in full. There is no version of this where leaving means losing the record of your own business.

The work this removes

Where the time actually goes

A year of one person

Writing the detail for a catalogue of a few thousand products — the description, the specification, the allergens or the materials, and the text a search engine reads. At a few minutes an item it is roughly a year of somebody at a desk, which is why most catalogues never get it.

Generated across the whole catalogue at once, including read straight off a photograph of the packaging, and reviewed by a person before anything is published.

Weeks → an afternoon

A new page. Not only a campaign landing — a category, a brand, an editorial piece, a corporate page. The usual route is a brief, a designer, a developer and a release window, so the idea is three weeks old before anyone sees it.

The person who wanted the page builds it from ready sections and publishes it. Every save keeps the previous version, so nobody is afraid to try.

One instruction

A change across the whole catalogue. Rewrite the search text for the top hundred sellers. Enrich a range that arrived with nothing but a name and a price. Build a landing page out of this month's best sellers before the meeting ends. Every one of those is normally a ticket, a spreadsheet, a sprint or an agency — which is why they mostly do not happen.

You say it, in a sentence, to the AI assistant your team already uses. It reaches the shop through an approval you grant from your own login and revoke in seconds, every change it makes is a version you can restore, and nothing reaches a customer until a person publishes it.

The choice

Three ways to do this

Approaches, not vendors — so it still holds when the names on your shortlist are different ones.

A central block with six mismatched machines bolted around it at different angles, each on its own tile.

A storefront, plus apps

Cheapest to start, and the widest choice of add-ons.

Picking, delivery, order management and collection are each a separate application — a licence, an admin screen, an integration and a support boundary each. The shop and the operation never quite agree, and the bill grows with the revenue.

A small complete shop standing inside a much larger enclosure, its door facing inward.

A marketplace, in your colours

Fastest to launch, and it arrives with an audience.

The storefront, the picking and the delivery are theirs. So is the customer: you rent the relationship and pay a share of every sale for as long as it lasts.

One housing, cut away: a shopfront, a rack, a packing bench and a van all inside it, joined by a single rail.

EazyShop

One system for the selling and the supplying.

The shop, the catalogue, the orders, the aisle, the van and the reporting on one set of facts and behind one login. Your tills and back office stay where they are. One team accountable when something breaks, and a bill that does not grow with your success.

Start here

Not a website project

A new operating model for the company. Point us at wherever your products already live and look at your own catalogue, at your own prices — and we will tell you, unasked, what we have not built.