A shop assistant completing a sale on the sell.ke POS, with a barcode scanner and a receipt printer on the counter

    Every channel, one ledger

    Omnichannel retail management, without the integration project

    Omnichannel is a word that usually arrives attached to a six-figure implementation. Strip the vocabulary away and it describes something very ordinary: a customer should be able to buy from you in whatever way suits them that day, and you should still have one accurate picture of your stock, your customers and your money afterwards.

    Most retailers already sell on several channels without calling it that. A counter. A website. Orders over WhatsApp or the phone. A delivery round. A wholesale customer with agreed prices who orders by email. Each one is a channel, and each one that lives in its own place is another version of the truth to reconcile.

    An omnichannel retail management system is simply one that treats those as views of a single business rather than as separate businesses that happen to share a name. That is an architecture decision, not a product tier — which is why it is available here at the price of a POS rather than the price of a project.

    What you get

    What this gives you

    One inventory behind every channel

    Counter, storefront, delivery and manual orders all draw on the same stock, per location. Nothing is allocated to a channel in advance, so nothing is stranded in the wrong one.

    One customer, however they bought

    Purchase history, credit balance, loyalty points and agreed prices belong to the customer, not to the channel. The regular who usually buys in person gets their pricing when they order online.

    Channel-tagged reporting

    Every sale records where it came from, so you can see revenue, margin and stock turn by channel and stop guessing whether the website is genuinely adding sales or moving existing ones.

    Fulfil from where the stock is

    An online order can be picked at the branch that has the item, collected in store, or sent out on a delivery round with its own zones and fees. The order and the stock movement stay connected throughout.

    Prices and promotions set once

    Price lists, customer-group pricing, discounts and promotional periods apply across channels from one definition, so a campaign does not have to be built twice and cannot be live in one place and expired in another.

    One ledger underneath

    Every channel's sales, refunds, costs and payments post into the same double-entry books, so the month-end position is a report rather than a reconstruction. Accounting from the Growth plan.

    Multichannel, omnichannel, and which one you actually need

    Multichannel means selling in several places. Omnichannel means those places behaving as one business from the customer's side and from yours. The distinction sounds like marketing until you meet it concretely: buying online and returning in store is an omnichannel behaviour, and it is straightforwardly impossible if the web orders live in a system the counter cannot see.

    Most independent retailers need far less than the enterprise version of this idea and get most of the benefit. Three things carry it: one stock figure, one customer record, and one ledger. Endless-aisle ordering, unified loyalty tiers across franchisees and predictive allocation are real capabilities, but they are not what is costing you an evening a week.

    So the practical target is not 'implement omnichannel'. It is: can a customer buy through any channel you offer, and can you answer what you have, what you sold and what you made without merging exports? If yes, you are running omnichannel retail regardless of what the software is called.

    The channels this covers, concretely

    The counter, including a second or third till on a busy day at no extra licence cost, and a phone or tablet for selling on the shop floor or at an event.

    The online store on your own domain, with categories, search, delivery zones and order management, generated from the same catalogue rather than maintained separately.

    Assisted and manual orders — a phone call, a WhatsApp message, a walk-in wholesale order — entered as orders against a customer record with their agreed prices, quotations where the sale needs one, and invoicing on account where the customer buys on credit.

    Delivery, with zones and fees, and the driver's round tied back to the orders it is fulfilling so an undelivered item does not vanish from stock.

    • In-store counter, multiple tills, no per-terminal licence
    • Mobile POS on Android for the shop floor, markets and events
    • Your own online storefront on your own domain
    • WhatsApp product sharing into a real order, not a screenshot
    • Quotations, credit sales and customer-specific price lists
    • Delivery zones, fees and fulfilment tracking

    What omnichannel usually costs, and why this does not

    The enterprise route to this is an order management system sitting above a POS, an ecommerce platform, a warehouse system and an ERP, wired together by an integration layer. The software licences are the smaller half of that bill; the integration work and its permanent maintenance are the larger half, and the reason mid-sized retailers routinely abandon the project half-built.

    The cost disappears when there is nothing to integrate. If the channels are views of one system, omnichannel is not a layer you buy and maintain — it is simply how the system behaves. That is the entire argument, and it is why a shop with two staff can have something an enterprise spent two years procuring.

    What you give up is the freedom to pick a best-in-class product for each layer. That is a genuine trade, and for a large retailer with a dedicated systems team it may be the wrong one. For an independent business, a coherent whole beats a collection of better parts that do not agree.

    Compare

    Three ways to run multiple channels

    What you are comparingSeparate systemsIntegration layer / middlewaresell.ke
    Stock across channelsSeparate figuresOne figure, eventuallyOne figure, by construction
    Customer recordOne per channelMerged by matching rulesOne, natively
    Buy online, return in storeNot workablePossible once builtWorks out of the box
    Time to runningImmediate, then permanent manual workMonths of implementationDays
    Who maintains the joinsYou, by handYou, or a paid partnerNobody — there are none
    Cost shapeSeveral subscriptionsLicences plus implementation plus upkeepOne subscription from USD 12

    Questions

    Omnichannel retail management — questions

    What is an omnichannel retail management system?

    Software that runs every channel you sell through off one set of records — one inventory, one customer database, one price and promotion definition, one ledger. The test is not how many channels it supports but whether a change in one is immediately true in all of them, and whether a customer's history follows them between channels.

    Do I need to be a certain size for omnichannel to be worth it?

    No — the threshold is channels, not revenue. A single shop that also takes WhatsApp orders and does deliveries is already running three channels and already paying the reconciliation cost. In practice the benefit arrives the moment you have two channels and a stock figure you cannot fully trust.

    Can customers buy online and collect or return in store?

    Yes. Because the counter and the storefront are the same system, an online order is visible at the till, can be marked collected, and can be returned or exchanged in person with stock and the ledger both updating correctly. This is the specific behaviour that separate systems cannot do without custom work.

    How do you handle stock when several locations could fulfil an order?

    Locations hold their own stock rather than pooling into one number, so the storefront can show honest availability and an order can be assigned to the location that has the goods — or collected from a specific branch. Transfers between locations are recorded movements, so the goods are never briefly in neither place.

    Does this replace an ERP?

    For an independent retailer, restaurant or wholesaler, it generally removes the reason they were considering one: inventory, purchasing, sales, customers and double-entry accounting in one place. It is not an ERP in the sense a manufacturer with a bill of materials, production scheduling and demand planning means — if that is your business, be sceptical of anyone, including us, who says it is.

    Can I run more than one location?

    Yes, from the Basic plan up. Locations share one product catalogue but hold their own stock, so moving goods between them is a recorded transfer rather than a re-count at both ends. Reports run per location or across all of them, and staff permissions are set per location — a branch supervisor does not need to see another branch's margins.

    How much does sell.ke cost?

    Plans run from USD 12/month for a single-location till to USD 115/month for unlimited scale, with the online store on your own domain included from USD 23/month. In Kenya the same plans are KES 1,499 to KES 14,999/month, billed in shillings. Every plan starts with a 14-day trial and no card, and there is no per-terminal licence and no commission on your sales. There is no hardware to buy either — sell.ke runs on a phone, tablet or laptop you already own.

    Which countries does sell.ke work in?

    The software is not geographically limited — the counter, inventory, the storefront, reporting and accounting work anywhere, in multiple currencies. What is market-specific is two things: the payment rails available to you, and your country's tax-invoicing rules. We currently run with merchants in Kenya, Uganda, Tanzania, Rwanda, Ethiopia, Ghana and Nigeria, and the deepest local payment and compliance integrations are in Kenya. If you are outside those markets, ask before you sign up and we will tell you precisely what would and would not be connected for you.

    How long does setup take?

    A single-counter shop is usually selling the same day. The work is the product list, not the software: import a spreadsheet, scan barcodes, or let Amina build products from a supplier invoice or a photo of your price list. A multi-location business with thousands of SKUs and opening stock counts should plan about a week and run the old system alongside for a fortnight. The 14-day trial is long enough to do exactly that.

    Try it on your own products

    Fourteen days, no card. Import your product list or let Amina build it from a photo of your price list, and run it alongside whatever you use now.