Retail Software Development One stock number across the till and the web
Point of sale, inventory, online store and accounting that agree with each other. We connect Shopify or Odoo where they fit and write custom code only where they do not, and we say which is which before you spend.
Five retail systems, built or connected.
The brief is nearly always the same: stop the shelf count and the web count disagreeing. These are the parts we build or connect to get there.
One inventory across stores and online
A single stock record that the till, the website and the marketplaces read and write, with reordering rules, counts and transfers between locations.
Point of sale and hardware
POS set-up on Odoo or Shopify, receipt printers, scanners, cash drawers and payment terminals, tested with the exact models you own.
Ecommerce and order handling
Online checkout, shipping options, returns and invoicing connected to stock, so an order placed online reserves the same unit a store would sell.
ERP, accounting and tax links
Integrations that move orders, stock, customers and tax between your store platform and the ERP or accounting system you already use.
Loyalty and reporting
Loyalty programs where your platform supports them, plus sales, margin and stock reports your buyers can read without a spreadsheet export.
Buy the platform, build the gap, and connect them so stock agrees.
In our experience the right first move is often not a custom system. Shopify, Odoo and similar platforms already cover checkout, point of sale and stock. Custom software earns its cost where a rule is yours alone, such as how bundles are priced, how a supplier feed lands, or how a return is routed. Devvista is a software development company that builds those gaps and the connections between tools for US merchants.
This page walks through the four routes (Shopify, Odoo, custom, or a mix), what each platform's own documentation says it can do, what is specific to US retail tax, and what a project costs. If your main need is the online store itself, our ecommerce development page and ecommerce software page go deeper on that side.
Where retail systems quietly break.
In our experience retail systems fail at the seams more often than inside a single tool. The till sells the last unit at 2 p.m., the website still shows it at 4 p.m., and an online customer is told two weeks later that the order is cancelled. A transfer between stores is recorded on paper and entered a day late. A promotion is set up in the store system and forgotten in the online one.
Each of these has the same cause: a stock figure, a price or a customer record is stored in two places and updated by hand in one. The fix is to decide which system owns each fact and to connect the others to it. That is as much a design question as a coding one, and it is where our first call spends its time.
A typical starting point: a retailer with a few stores and a web shop, a POS from one vendor, an online store from another, and a spreadsheet that reconciles them on Mondays. The aim is to replace the spreadsheet with a connection, not to replace everything.
Shopify, Odoo, custom code, or a mix.
The table summarises what each route is, using each vendor's own documentation for the facts in the second column.
| Route | What the documentation says | Fits when |
|---|---|---|
| Shopify with Shopify POS | Shopify POS is a point of sale app for iOS or Android that tracks orders and stock across retail locations and the online store from the Shopify admin, with multi-location enabled in settings; barcode scanners and cash drawers can be connected. | Retail is store-front plus web, the catalogue is product-led, and you want a hosted platform. |
| Odoo (POS, eCommerce, Inventory) | Odoo describes its Point of Sale as designed for shops and restaurants, eCommerce as an online store platform, and Inventory as both an inventory application and a warehouse management system. | You want store, web, stock, purchasing and accounting in one database. |
| Custom software | Not a product: scoped around your own rules, on a stack we agree with you. | A rule is unique to you and no platform models it. |
| Platform plus custom layer | Platform for the standard flow; custom code for the specific rules and for connecting systems. | Often a good fit for mid-size retailers. |
Which route is best depends on your store count, catalogue size and the tools you already pay for. If you are on another platform and weighing a move, see our Shopify migration page and Shopify app development.
Inventory that stays true across store and web.
Whatever platform you pick, the stock record is the heart of the design. Odoo's Inventory documentation lists lot and serial tracking, reordering rules, routes and push and pull rules, cycle counts, warehouses, inter-warehouse replenishment and dropshipping (barcode has its own section). In our view those are the pieces a retailer needs most. Shopify's help describes tracking stock across retail locations and the online store once multi-location is on.
We design the flow around events, not screens: a sale, a return, a transfer, a stocktake and a supplier receipt each change stock in one defined way, in one system, and every other channel reads from it. Odoo's eCommerce documentation names Google Merchant Center, which can also feed product listings to TikTok, Facebook and Instagram. Marketplaces are the usual weak point of any stock design, so we can review what each connector you are considering supports for your catalogue before a sync is promised.
If you run Shopify with a separate ERP, our Shopify ERP integration guide explains the common patterns and pitfalls.
POS and hardware: what to check before you buy a terminal.
In our experience hardware causes more launch delays than software. Odoo's Point of Sale documentation lists receipt printers, customer displays, scales, electronic shelf labels and IoT connections in its hardware section, and payment terminals under payment methods, alongside cash machines, customer accounts and QR code payments. It says the system is built to maintain functionality during temporary network outages, without further detail in the overview. Shopify's POS page lists barcode scanners and cash drawers as connectable equipment and points to a hardware guide.
Before quoting, we can ask for the exact models you own or plan to buy and run each through a staging test (print, scan, charge, refund, close the day), writing down what fails. Card payments and receipts are tested end to end, because a till that cannot take a card on opening day is a bigger problem than any missing feature.
Ecommerce, ERP and accounting that share one set of books.
Once orders arrive from several places, the questions become financial: which system issues the invoice, where a refund is booked, and how stock value reaches the ledger. Odoo's eCommerce documentation covers order handling from sale through abandoned carts, delivery, stock, returns and invoicing, and delivery options at checkout. If you run another platform, we build the same chain through its API and webhooks.
Loyalty and reporting follow the same rule. Odoo lists loyalty under shared extra features of Point of Sale and covers order and session statistics in its reporting. Where you use another platform, we keep one source for customer and points data and feed reports from it. Our guide on webhooks versus APIs explains how those links are built, and our Odoo implementation page explains how an Odoo project is scoped.
US sales tax: one place where retail software has to be set up with care.
Odoo's AvaTax page describes an integration with Avalara for real-time, location-specific tax calculation when you sell, purchase and invoice. It is available for companies located in the United States, Canada or Brazil, requires your own Avalara account and license key, uses the company address by default (to use the warehouse address, Odoo says to enable Allow Ship Later in the Point of Sale app settings), and does not support excise taxes such as those on tobacco, vapes and fuel.
For a retailer with several stores or warehouses, that default matters, so we check how each location's address is handled during testing. We do not decide what tax applies to your products or states. That is for your tax adviser, and we configure what they tell us.
When custom retail software pays for itself.
Use this as a quick screen before you ask for a quote.
| Situation | Likely answer | Why |
|---|---|---|
| One store and a web shop, standard catalogue | Buy a platform, add apps | Checkout, POS and stock are already covered; custom code adds cost. |
| Stock disagrees across channels | Buy plus integration | The fix is a connection with one owner of stock. |
| Pricing or bundle rules unique to you | Platform plus custom layer | Keep the standard flow and own only the special rule. |
| Unusual fulfilment or supplier flow | Custom module or service | No package models it; a small module is cheaper than a full system. |
| Everything about your model is unusual | Custom software | Uncommon in our experience; confirm with a discovery call before committing. |
If you are a start-up testing a retail idea, our start-up software page covers a lean first build. For wider custom work, see custom software development.
What retail software costs, and what moves the price.
After a short call we write the quote to your scope, and we ask for the budget range you have in mind so we can propose what fits. What moves the cost is the scope, the number of integrations, who does the work and how settled the requirements are. What moves the price:
- Number of locations, tills and sales channels.
- Size and quality of the product catalogue and its history.
- Number of systems to connect and how good their APIs are.
- Tax set-up across locations.
- Custom rules, such as bundles, supplier feeds and returns routing.
- Hardware testing and training.
To get a figure for your shop, ask for an estimate and list your channels, tools and the three problems that cost you the most time.
Three habits behind our retail projects.
Platform first
We usually start from what Shopify or Odoo already do and write code only for the gap. It keeps cost and maintenance down and makes upgrades simpler.
One owner for each fact
Stock, price and customer data each get one owning system. Every other channel reads from it, so a number is never typed in two places.
Hardware checked early
Where it applies, printers, scanners and terminals can be tested on a staging build before launch, with the results written down.
From the first call to stock that agrees everywhere.
Each step is checked on a staging copy before it touches live data.
Book a callWhat we checked before writing this page.
Vendor documentation pages opened on 9 November 2026. We state only what the pages say; where an overview did not say something, we left it out.
- https://www.odoo.com/documentation/19.0/applications/sales/point_of_sale.html: Point of Sale intro, hardware list, payment methods, loyalty, offline statement, reporting
- https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory.html: Inventory as inventory application and WMS; barcode, lots, reordering, routes, cycle counts, dropshipping
- https://www.odoo.com/documentation/19.0/applications/websites/ecommerce.html: eCommerce overview: order handling, delivery options, Google Merchant Center, marketplace connectors
- https://www.odoo.com/documentation/19.0/applications/finance/accounting/taxes/avatax.html: tax integration details
- https://help.shopify.com/en/manual/sell-in-person/shopify-pos: Shopify POS: iOS or Android, orders and stock across retail locations and online store, multi-location setting, scanners and cash drawers
Case studies
None of our published case studies is a retail store or POS project, so we show none here. The closest public example of a custom booking and ordering platform is Discovery89, which is travel, not retail.
Questions retailers ask before a first call.
Straight answers to the questions buyers ask before a first call.
Ready to make your tills, your website and your books agree?
Tell us your channels, your current tools and the three problems that cost you the most time. We will come back with a route, a price range and an honest view of build versus buy.
- 30-minute consultation
- No commitment required
- Response within 24 hours
- Book a call30 minutes, no pitch. Tell us what you want to build.
- Get a straight answerHonest feedback on fit, scope and timeline.
- Decide with no pressureMove ahead only if it feels right. No commitment required.