Skip to main content
Have a project in mind? Let's talk
Book a call Tell us about your project Book a Call
POS
  POS Software

POS Software Development. Retail and Restaurants.

Devvista builds custom point of sale software for US retailers, restaurants and service businesses: the register, the card terminal link, stock, accounting and the online store, working as one system. If an off-the-shelf POS fits your shop better, we say so before any code.

Sales taxBy place of sale
OfflineSell through outages
HandoverCode and Documentation
Retail POS Restaurant POS Sales Tax Rules Card Terminal Integration Offline Mode Inventory Sync Accounting Link Online Store Link Retail POS Restaurant POS Sales Tax Rules Card Terminal Integration Offline Mode Inventory Sync Accounting Link Online Store Link

What Is a Custom POS Project?

A till that rings up sales is the easy part. The work is making the tax, the card terminal, the stock count and the books agree at close of day.

Devvista is a software development agency that builds custom POS software for US businesses: counter and tablet registers, a back office, and the links to your payment processor, accounting file and web store. Most shops should start by asking whether a packaged product fits. We build when your sales process does not, or when running three disconnected tools costs you more in rework than one joined system would.

A POS is a business system, so it is built like one. It shares ground with our custom software development work, and when the till has to sit inside a wider ERP we do that through Odoo implementation. If the web store is the main channel, read about ecommerce development first.

Buy, integrate or build. The honest choice depends on how unusual your sales process is.

RouteBest forLimit to know
Subscription POSStandard retail or cafe trading with a normal catalogueYou adapt to its workflow and data model
Integrated POSA packaged till plus custom links to your accounting, stock or web storeDepends on what the vendor's API exposes
Custom POSUnusual flows: quotes at the counter, appointments, rentals, multi-step ordersYou own and maintain a product, so it needs a plan for updates

Describe how one sale runs today. That is enough to tell you which row you are in.

Get a Quote

POS Development Services

Six parts of a POS, scoped as separate lines so you can see what each one involves.

01

Register and Counter App

A fast sales screen for tablet, desktop or handheld: catalogue search, barcode scan, modifiers, discounts, split bills, returns and staff permissions. Built around the hour your shop is busiest.

Register
02

Payment Terminal Link

Integration with your processor's public API or SDK so the card is taken on its certified reader.

Pay
03

Sales Tax Engine

Rates by place of sale, exempt and resale flags, and the rate stored on every line.

Tax
04

Inventory and Back Office

Stock counts by location, purchase orders, transfers, low-stock alerts and a single record shared with your web store, plus the reports a manager reads at close: sales by hour, by staff and by tender.

Stock
05

Accounting Integration

Daily or per-shift postings with tax, tips, processor fees and payouts on separate lines so the deposit reconciles.

Books
06

Offline Mode and Receipts

A register that keeps selling through an outage, then syncs. Printed, emailed and texted receipts with a tax breakdown.

Offline

What a US POS
Has To Handle.

The parts of selling in the United States that decide whether a POS design holds up. Facts below link to their sources at the foot of the page.

TopicWhat is trueWhat we build for it
Sales taxState rates differ, and local rates vary widely inside states. The Sales Tax Institute's rate chart (as of 11/1/2026) says rates change monthly and that the specific jurisdiction rate should be used for accurate calculations.Rate lookup by location, rate stored per line, exempt and resale marking, and an export your tax adviser can file from.
Card dataThe PCI Security Standards Council says its standards are meant for entities that store, process or transmit payment account data, and for developers of software and devices used in those transactions.A design in which the card is read on your processor's terminal and the POS only receives a result and a reference. What applies to your business is confirmed with your processor.
Offline sellingStripe Terminal can store payments on the device and forward them when the connection is restored, with listed exclusions such as QR payments and swiped cards.Rules for which tenders and amounts are allowed offline, and a clear status on stored payments.
Terminal integrationSquare documents a Terminal API for sending checkout requests from a POS application to a paired terminal, with results by webhook or query.Integration against the processor's public API, with retries and duplicate-payment protection.
TippingStripe lists on-reader tipping as supported on smart readers but not on mobile or Tap to Pay readers.Tip prompts, tip pooling and tip reporting that matches your payroll process.

We do not claim any compliance status for a system on your behalf. What the build does is keep card data away from your own database where the processor allows it, and leave a clear record of each sale for your accountant. Ask your processor and tax adviser what applies to your business.

Retail, Restaurants
and Services.

Each type of business stresses a different part of the till. We start from the one that hurts most.

BusinessWhat the register must doTypical integration
Specialty retailVariants, serial numbers, layaway, returns with store creditWeb store stock and accounting
Restaurant and cafeTables, courses, kitchen tickets, split checks, tipsKitchen display, payroll, delivery orders
Service businessAppointments, deposits, packages, invoices at the counterBooking, CRM and text-message payment links
Multi-location groupCentral catalogue, local prices, transfers between sitesERP, consolidated reporting

For the wider retail picture, see retail software development. If your sales also happen in an app, our mobile app development team can build the customer or staff side.

Stripe Terminal Square APIs Clover APIs React Flutter Node.js Python PostgreSQL Odoo

From Counter Walk-Through.
To Live Registers.

A POS goes live in a shop that is open. The plan below keeps the old way of selling available until the new one has been proven.

01
Step One

Watch a Real Shift

We map how a sale, a refund and a close-out actually run, including the workarounds staff use today.

02
Step Two

Pick Processor and Hardware

We confirm which processor, terminals and printers you use and read their developer documentation before promising any feature.

03
Step Three

Design the Tax and Stock Model

The data model comes before the screens: tax rules, locations, units, variants and how each posts to the books.

04
Step Four

Build and Test on Real Terminals

We test with test-mode payments on actual readers, including declines, cancellations and pulled network cables.

05
Step Five

Pilot in One Location

One register runs the new system next to the old one for a defined period, and we compare the end-of-day totals line by line.

06
Step Six

Roll Out and Support

Staff training notes, a rollback plan, and a support arrangement for updates when processor APIs or tax rules change.

What You Can
Check Early.

Things you can test in the first weeks instead of taking on trust.

01
A Straight Buy-or-Build Answer

If a packaged POS does the job, we will say so and help you connect it rather than rebuild it.

02
Your Merchant Account Stays Yours

Payments settle through your own processor account. We build against its API and never sit in the money flow.

03
Reconciliation You Can Audit

Every sale keeps its tax rate, tender, tip and processor reference, so a daily total can be traced to its lines.

04
Ownership Agreed in the Quote

Who owns what is set out in your contract, and we can work in repositories under your company.

POS Questions,
Answered.

What owners ask before they replace or build a point of sale.

Still have a question?Send it over and we will answer personally.Get a Quote

Subscribe when your trading is ordinary: one or two shops, standard tax handling and a stock list that fits a template. Build when the till has to follow a process the packaged products cannot, such as quoting and invoicing at the counter, rental or appointment billing, a vendor-specific catalogue, or a single stock record shared with your own web store and accounting file. We will tell you if a subscription POS is the better buy for your case.

It looks up the rate from the customer's place of sale or delivery instead of holding one fixed percentage. Local rates differ widely inside a single state, and the Sales Tax Institute notes that the specific jurisdiction rate should be used for accurate calculations. We connect the till to a tax rate service or your accounting tool, store the rate that was applied on every line, and keep exempt and resale sales marked so the return can be built from the data.

The design goal is that it never does. The card is read on a payment terminal that belongs to your processor, and the POS only receives a payment result and a reference. Stripe's own documentation describes the reader securely holding payment information itself and forwarding it, not the POS app. Which card-data rules still apply to your business depends on the processor and your setup, and that is a question for your processor and acquirer. We do not certify your business for you.

Yes, within limits. Stripe Terminal can store payments on the device and forward them once the connection returns, but its documentation lists exclusions: some card brands and QR payments are not supported offline and swiping is not allowed. We design the offline path around those limits: which tenders are allowed, a ceiling per sale, how the register shows an unconfirmed payment and what happens when a stored payment is later declined.

We build against the public developer APIs of the processor you choose. Square documents a Terminal API that lets a POS application send checkout requests to a paired Square Terminal and learn the result through webhooks, and Stripe documents the Terminal SDKs and server-driven options. Clover and others publish their own developer programmes. The right pick depends on your fees, your terminal hardware and where you already hold a merchant account.

It can. The tip screen is shown on the reader where the processor supports it. Stripe's documentation, for example, lists on-reader tipping as supported on smart readers but not on mobile or Tap to Pay readers. We decide the tip flow with you: percentage buttons, custom amounts, tip pooling between staff and how tips appear in payroll and tax reports.

Chip and contactless acceptance are handled by the certified reader, not by your software. What we build is the surrounding behaviour: the register waiting for the terminal, handling a cancelled or declined tap, partial approvals, refunds back to the original card and a clear record of each attempt. Picking a reader that your processor already supports keeps certification out of the project scope.

That works for deposits, balances and remote orders if your processor offers hosted payment pages. The customer pays on the processor's page, so card details do not pass through your system, and the POS marks the sale paid when the confirmation arrives. We add reminders, expiry times and a way to void the link if the order changes.

Through the accounting tool's API or an export your bookkeeper already uses. Each sale posts as a summarised entry per day or per shift, with tax, tips, fees and payouts on separate lines so the bank deposit reconciles. If you run an online store, we keep one stock record so a sale in either place updates both. Our ecommerce and Odoo pages cover that side in more depth.

A short description of how a sale runs today, the payment processor and hardware you use or are considering, the accounting tool, and the places you sell. A walk-through of one busy hour at the counter is more useful than a long specification. We reply with the questions that matter and, after a short call, a written proposal to scope.
Let's talk

Tell Us How You Sell.

Walk us through one busy hour at your counter. We will reply with the questions that matter and, after a short call, a written proposal to scope.

  • Online consultation
  • NDA signed on request
  • Reply within 24 hours
  1. Book a call30 minutes, no pitch. Tell us what you want to build.
  2. Get a straight answerHonest feedback on fit, scope and timeline.
  3. Decide with no pressureMove ahead only if it feels right. No commitment required.
Chat on WhatsApp