Stores · Online shops · Counters

ERP for retail and e-commerce

The retail counter is one part of the business. A completed sale must also explain which stock left the store, how the customer paid, and what the financial records show.

In short

Connect the till, the stock movement, and the day’s money. Can the store explain a sale, return, tender, and cashier count without reconstructing them in separate systems?

Problems it solves

Run the shop counter and the online store from one operational picture, with shared pricing, stock and the financial documents behind each sale.

01

Cashier activity disconnected from the books

Use company-scoped terminals and cashier sessions, with the existing product, customer, tax, and payment-method masters.

02

A sale that leaves the warehouse picture behind

Follow the completed sale through its Inventory delivery, Finance invoice, and receipts for the permitted tenders.

03

Returns that correct only one part of the transaction

Review the stock return, financial credit note, and refund accounting together, including the relevant session cash effect.

04

A second catalogue for the online store

Publish existing Inventory products to the E-commerce store with live prices and availability, so the website and the counter sell the same stock.

A typical day

A typical day

  1. A cashier starts the session at the configured terminal.

  2. The customer’s items are priced using the applicable product and commercial setup.

  3. The cashier accepts a permitted tender and completes the sale.

  4. The supervisor reviews the associated stock and financial documents.

Who does what

Who does what

RoleModulesWhat they do
CashierPoint of SaleOpen the permitted session, build the basket, accept eligible tenders, and complete the retail sale.
Store supervisorPoint of SaleReview restricted discounts, authorized returns/refunds, and cashier-session validation.
Stock teamInventoryFollow deliveries, returns, tracking, and the stock position behind the sale.
Accounts teamFinance + ReportsInspect invoice/receipt posting and the financial view of the retail activity.

Decisions it supports

Decisions it supports

  • Cashier accountability

    Compare sales tenders, returns, cash in/out, and the counted session position.

  • Return handling

    Follow the original sale, returned goods, credit note, and refund rather than correcting only the till total.

  • Offline policy

    Decide which captures are permitted while disconnected and inspect replay/synchronization outcomes.

Exceptions handled

Exceptions handled

SituationWhat happensModules
A cashier needs a restricted discountThe configured cashier/supervisor boundary determines the approval.POS policy
A customer returns an earlier purchaseThe authorized return follows stock, credit-note, refund, and session-cash treatment.POS + Inventory + Finance
The store loses connectivityOnly the configured offline path captures work; the queue shows the server validation result.POS offline policy

What we set up

What we set up

  • Company/branch POS policy, terminal locations, permitted journals, and payment methods.

  • Cashier/supervisor roles, session-opening rules, and return authorization.

  • Product barcodes, eligible prices/promotions, print formats, and any scale interface.

  • Offline capture/replay policy and physical printer acceptance.

Bring these to the demo

A sale paid with the payment methods your store uses. · A returned item and its refund accounting. · Cashier and supervisor permissions, including the configured offline policy.

Does POS use separate products and customers?

POS consumes the existing shared masters, including products, customers, warehouses, taxes, price lists, and payment methods. The terminal’s company and branch context still applies.

Does offline selling mean a transaction is already posted?

No. Offline selling is subject to the configured POS policy and replay validation. Ask to see both the capture and the subsequent validated posting flow.

What is a retail POS workflow in Prospiro?

It is the cashier’s terminal/session process: prepare a basket, resolve product prices and offers, accept eligible tenders, and complete a sale with its stock and financial records. Session review accounts for the cashier’s sales, returns, cash movements, and count.

Can a customer split the payment for one sale?

The terminal’s tender configuration determines which payment methods and combinations are permitted. Review the accepted amounts, change/refund rules, and the sale-linked receipts with the applicable customer and session context.

How are a return and a cash refund related?

A return identifies the eligible goods and original sale context. The permitted refund records the financial settlement under the configured controls. Review both the physical stock result and the money movement; a returned item does not itself prove that the cashier paid out the correct amount.

What happens to a sale made offline?

The configured offline policy determines what the terminal may capture. The queued sale must synchronize and pass server-side replay validation before final posting. A locally captured basket or payment is therefore distinct from a completed delivery, invoice, and receipt.

Book a demo

See Prospiro run your own process.

Tell us what you sell, stock and deliver. We plan the session around the modules you need, in English or Arabic.

  • Built around your products, routes and documents
  • Includes the exceptions, not only the happy path
  • Your request goes straight to our team

Prefer email? info@prospiro.ai

What do you want to see?
We use your details only to reply to your request and follow up on it. Privacy policy
VAT calculator