Most WooCommerce plugins give you a till, and leave the stockroom to somebody else. Or they give you a stockroom that has never taken a sale. CodeBold Commerce does the whole shop — order it, receive it, label it, sell it, cash up, count it — inside the WooCommerce you already run, on your own server.
Free core on WordPress.org · Self-hosted · GPL
A till that cannot raise a purchase order still leaves you ordering stock in a spreadsheet. A stockroom that cannot take a sale still leaves you typing the day's takings in by hand. Either way you are running two systems and reconciling them on a Sunday.
Scan or search, variant badges on the tile, park a sale, split the tender, refund by receipt number, open and close a shift with a float and a Z report.
Suppliers with lead times, purchase orders, receiving, weighted-average costing, stock takes, transfers between outlets, barcode labels. Not an add-on. In the box.
Sales are written through WooCommerce's own order system. The counter, the website and your accountant read the same figure, because there is only one figure.
Install a plugin, open a page, sell. There is no separate account to create, no catalogue to import, no app store, and nothing to keep in step overnight. The products are the products you already have; the orders are the orders you already read.
It is meant for the person standing at the counter. Not a warehouse team, not a franchise chain — a shop with one till, or four, and a stockroom behind it.
It starts with a supplier, not a sale. Suppliers carry lead times, so reordering stops being a guess about when the van turns up.
You need kurtas in 3 colours and 4 sizes. Tick the boxes instead of writing twelve lines.
Ordering 0 pieces. They arrive in about 12 days.
This is where cost is learned. Record what actually arrived — not what you ordered — and the weighted-average cost updates itself. Margin stops being a guess too.
You ordered 40. Count what is actually in the box.
0 turned up.
Each one really cost — — worked out from this invoice and the last one, so you never have to.
Stock that arrived without a barcode gets one. Print a test sheet first, so you are not burning a roll of labels finding the alignment.
It came without a barcode. Give it one.
Stick it on and the scanner knows it.
Scan a barcode and it is on the sale. No barcode, or a garment that never had one? Search by name and pick the variant from badges — so the cashier is choosing, not reading.
Beep. Beep. Beep. Three things on the counter.
Print an X report mid-shift to check without closing. At the end, count the drawer and print the Z: what the till expected, what you counted, and the difference in one line.
Count the drawer. The till already knows what should be in it.
Small enough to be a wrong bit of change. Big enough that you want to know.
The system's own figure is hidden while you count. Deliberately — seeing it first turns a stock take into a rubber stamp. Type what is on the shelf, then see the variance.
The screen will not tell you its own number until you have written yours down.
Seeing the figure first turns a count into a rubber stamp.
There is no cloud service in the middle of this. The till talks to your WordPress site and nothing else. Your sales, your costs, your customers and your margins stay on hosting you control, in the database you already back up.
That is not a philosophical point. It decides what happens when a vendor changes their pricing, gets acquired, or has a bad afternoon. A subscription here buys updates and support. It does not buy permission to keep selling.
One hop. Nothing in between to go down, change hands, or start charging per outlet.
We are going to be straight about this, because you will find out in week one anyway. The till has two tender types: cash and card. Cash calculates the change. For a card, the cashier charges it on the machine already sitting on your counter, then presses Card — and the order is marked paid with the tender recorded against it.
No browser-based till charges a card. A terminal does. Anyone telling you their web till processes the payment is describing an online checkout with a keypad drawn on it.
Your website is untouched by any of this. Razorpay, Stripe, PayPal — whatever gateway your shop runs online keeps running online, exactly as it does today.
Change calculated. Cash in, cash out and safe drops logged against the shift.
Charged on your terminal, recorded on the order. One sale, one record, nothing to match up later.
₹2,000 in cash and the rest on a card is one sale with two tender lines — not two sales.
Cash and card ship, and those are the two the till knows. A developer can add others — UPI, cheque, on account — through a filter, and they show up at the counter and on the Z report like the built-in two. Gift cards are not among them: that is store credit, which the plugin does not keep.
WooCommerce’s own tax engine, not a second one. The GST you set for your website is the GST charged at the counter, broken down by rate on the receipt, with a live preview before anything reaches the paper. Filing stays with your accountant.
Plenty of software greys out a button and calls it security. A hidden link is still reachable by typing the address into the bar. Ours refuses: every screen checks the capability twice — once when the menu is registered, and again when the page renders.
Twenty-six capabilities in four groups — four for the suite, twelve for the till, eight for inventory, two for membership — and four ready-made roles you can use as they are or take apart. Each capability is separate, so a cashier can refund without being able to discount.
One thing it will not do: lock an administrator out of their own site. That guard is deliberate.
The twelve till capabilities. Inventory, suite and membership groups are on the Members page.
Plenty of tills claim to work offline. The hard part is not holding a sale on a device — it is what happens when two of them come back at once. Receipt numbers here are reserved in advance, so two tills selling through the same outage cannot print the same number, and the sync tells you exactly what went through and what did not.
The screen, the products and the prices are cached. If the connection goes mid-queue, the cashier carries on: the sale is taken, the receipt prints, the change is counted.
Numbers reserved up front · queued on the device · reported on return
Plugins that keep sales in their own tables leave you with two sets of figures and an evening spent reconciling them. Here every movement is written through one path — and nothing moves without the ledger recording who, when and why.
Blue kurta, size M — watch both numbers
| Movement | Who | Why | Change |
|---|
Each one works on its own. Together they cover the stockroom, the counter and the shop front.
The till and the stockroom. Scanning, split tenders, shifts and Z reports, suppliers, purchase orders, receiving, stock takes, transfers between outlets.
Free core + add-onOpen →Tables, open tabs, order types, modifiers and kitchen tickets that colour as they age. Nested recipes take ingredients out of stock when a dish sells.
Optional moduleOpen →Twenty-six capabilities, four ready-made roles, and a check that runs twice — at the menu and at the page. Not paid memberships; the name misleads.
Free on WordPress.orgOpen →Filter the shop by attribute, price and availability, behind a Filter button on mobile. Sizes come from the product's own attributes, so a new size appears on its own.
Free on WordPress.orgOpen →A heart on the product card. Shoppers who are not signed in still get a wishlist, and it follows them when they make an account. Imports YITH wishlists with their dates.
Free on WordPress.orgOpen →This is why an ordinary shop plugin watches a café's stock never move. A dish is not a product on a shelf — it is made of things, and some of those things are themselves made of things.
A recipe can contain a recipe. Sell one burger and everything underneath it comes out of stock, at what those ingredients cost today.
Size and colour badges on the tile, a size-by-colour grid on purchase orders, and stock takes that survive a rail of forty variants.
TradesRead →Fast scanning, a queue that keeps moving, suppliers with lead times for the lines you reorder every week.
TradesRead →Tables, open tabs, modifiers, kitchen tickets that age visibly, and recipes that take real ingredients out of real stock.
TradesRead →Cost learned at receiving and carried through, permissions that keep cost prices off the shop floor, and a ledger behind every movement.
TradesRead →Automated tests · 41 suites · real WordPress · real database
Not mocks. Each test drives the plugin the way the till does — through its own REST routes, against live orders. It is the reason we can change the payment screen on a Friday.
Nothing changes stock without recording who, when and why. It is the answer to "where did those six go?"
Handed out in advance, so two tills selling through the same outage cannot print the same number.
The suite runs a real clothing retailer. That is one deployment, described as one deployment. No install counter, no logo wall — we would have to invent them.
For one counter, and for finding out whether this suits your shop.
For a shop that has outgrown one till, or thirty products.
For more than one room, or a kitchen that needs telling.
For a chain, where the number of shops is not a fixed number.
Every plugin is GPL. The subscription pays for updates and support, not for permission — whatever you have installed keeps working whether the key is active, expired, or never entered.
The core is free on WordPress.org. Put it on a staging site this afternoon and decide for yourself.