Both on your
server. One
brought a stockroom.
wePOS is a self-hosted WooCommerce point of sale — it runs inside WordPress, with no vendor cloud in the middle. On the question that separates us from most hosted tills, we agree with them.
So this comparison is not about architecture. It is about scope: a till on its own, or a till and the supply side behind it — suppliers, purchase orders, receiving, weighted-average costing, blind stock takes, transfers between outlets.
The parts that
do not change
with a release.
Scope
wePOS is a point of sale. We are a point of sale and a stockroom in one install. If your stock arrives from suppliers on lead times and you care what a piece really cost, that difference is the whole decision.
Where cost comes from
Ours is learned at receiving and carried forward as a weighted average, so margin is a figure the system already holds. A POS-only plugin generally takes cost from whatever is on the product, which somebody has to keep true by hand.
Counting stock
Blind stock takes with the variance held back until your count is committed, plus a ledger recording who, when and why on every movement. This is stockroom machinery rather than till machinery.
Permissions
Twenty-six capabilities across four groups, each separate, checked twice — at menu registration and again at page render. A cashier who can refund but not discount is a role you build without touching code.
Where we agree
Self-hosted, sales written as WooCommerce orders, a browser till with no app to install, a free version on WordPress.org that is genuinely usable. If those are your criteria, both of us pass.
Row by row.
Our column is what the suite does today. The other column describes wePOS as we understand it — check it against their own documentation before you decide, because it is their product to describe.
| Feature | CodeBold Commerce | wePOS |
|---|---|---|
| Runs entirely on your server | Yes | Yes |
| Sales written as WooCommerce orders | Yes | Yes |
| Browser till, no app | Yes | Yes |
| Free version on WordPress.org | Yes, not time-limited | Yes |
| Barcode scanning | USB or Bluetooth, or search by name | Yes |
| Card charged by the till | No — charged on your terminal, recorded on the order | No browser till charges a card |
| Suppliers with lead times | Free | verify |
| Purchase orders and receiving | Free | verify |
| Weighted-average costing | Free | verify |
| Blind stock takes | Free | verify |
| Stock ledger with who / when / why | Yes, on every movement | verify |
| Shifts with X and Z reports | Free | verify |
| Offline selling | Yes, with receipt numbers reserved in advance | verify |
| Transfers between outlets | Multi-outlet tier | verify |
| Restaurant recipes and tickets | Restaurant module, multi-outlet tier | verify |
| Licence | GPL, every plugin | verify |
TODO: verify every claim in the wePOS column against their current documentation, and date this page
When to pick
wePOS.
A comparison page that cannot name a single reason to choose the other product is an advertisement wearing a table for a hat. Here are the honest ones.
- If you genuinely only need a till — you buy finished goods, cost never moves, nobody raises a purchase order — a POS-only plugin is a smaller thing to install and a smaller thing to learn.
- weDevs has a large catalogue of WordPress plugins and a long track record, which matters if you already run several of them and want one vendor.
- A simpler product has fewer settings to get wrong on the first afternoon.
- Their pricing is published and easy to read. TODO: remove this line once our pricing is published
Switching.
We already run wePOS. Is switching disruptive?
Can I run the two side by side while deciding?
Do I need the add-on to replace a POS-only plugin?
Which one is faster at the counter?
Do not take our word.
Run both on staging.
Our core is free and not time-limited. An afternoon with your own catalogue beats any comparison table, including this one.