Divergent prices and promotions
The visible price, commercial rule and price actually applied do not always share the same version.
HERALD POS · Point of sale
Streamline checkout.
Connect the store to central systems.
HERALD POS structures items, prices, baskets, payments, receipts, returns and closing, with defined exchanges to the responsible systems.
01 / 03
Breaks at the counter
What slows sales and weakens control.
Hard-to-explain closing
Sessions, payments, cancellations and evidence are reconciled late or outside the system.
Return without context
Receipt, item, reason, right and inventory or financial impact are not systematically connected.
Limited network visibility
Each point of sale has a different view of activity, variances and events to handle.
A controlled store journey
From opening to closing, every transaction retains its context.
Operational benefits
A fluid experience without sacrificing explainability.
A fluid counter experience with consistent data between the store and central systems.
01
Checkout guided by context
Items, quantities, prices, promotions, customer and operator rights are brought together in one coherent journey before payment.
Test a scenario
02
Exceptions handled without hiding the rule
Discounts, cancellations, returns and corrections retain reason, owner, approval and impact according to the selected configuration.
Test a scenario
03
Closing based on explicit reconciliations
The session reconciles transactions, payment methods, cancellations and evidence without confusing authorisation, settlement and accounting.
Test a scenario
04
Network visibility defined by rights
Store, region and head office view the activity, variances and priorities within their scope, based on approved indicators.
Test a scenarioStore lab
Decide on the exceptions that really matter.
Source price, applied price, rule, author and reason retainedSituation
Price variance at checkout
The shelf price differs from the price calculated at checkout.
Signals to verifyItem, site and effective dateApplicable price and promotionCorrection right
Expected decisionIdentify the responsible rule, apply the authorised resolution and retain the rationale without silently changing master data.
Retained evidenceSource price, applied price, rule, author and reason retained
Functional scope
Explore HERALD POS without turning the page into a catalogue.
Selected capability
Checkout
Sale, payment, receipt and authorised operations.
- The basis, work unit, price, tax and period for « Checkout » are explicit before calculation.
- Every « Checkout » amount remains supported by the operations and rules that produced it.
- A « Checkout » variance, credit or rejection is assigned with a reason and resolution status.
Foundation and extensions
Compose the scope around the real store.
The sales foundation can be extended with ERP scope and suitable interfaces. Exact composition depends on version, network and architecture.
HERALD POS foundation
Point of sale, multi-store, tills, items, inventory, purchasing, sales, prices, catalogues, discounts, opening and closing.
Optional ERP module
Extended master data, quotes and contracts, advanced inventory, ERP connections and additional views according to the approved scope.
Interfaces & EDI
Structured files, shared database or REST APIs can be assessed flow by flow, with explicit responsibilities, errors and recovery.
System responsibilities
The till executes the sale. It does not replace the rest of the information system.
HERALD owns the till session, basket and authorised operations. ERP, OMS, WMS, payment provider and accounting retain their own responsibilities.
Store session and sale
Owns till session, basket, authorised operations, receipt, return and closing according to configuration.
- Basket and applied price
- Transaction and evidence
- Session and closing
Master data, promise and execution
Retain items, commercial rules, orders, stock promise and physical execution according to defined responsibilities.
- Item, price and availability
- Order and reservation
- Physical stock and fulfilment
Authorisation, settlement and accounting
Payment provider and finance own authorisation, settlement, statements and entries under their own rules.
- Authorisation and identifier
- Settlement and reconciliation
- Entry and period
Customer identity and journey
Identity, consent, loyalty and digital journey remain governed by selected systems and their exchange contracts.
- Identity and consent
- Loyalty and benefit
- Order and channel
Retail architecture
A store connected through explicit exchange contracts.
Every flow defines source, owner, frequency, rights, controls, errors and recovery. No universal connector, real-time or offline mode is assumed.
HERALDPOS
ERP
Inventory
POCKET CRM
Payment
E-commerce
BI
Store devices
Multi-site
Controlled deployment
Start with one complete store day.
Observe
Store, roles, day, exceptions
Scope
Items, prices, payments, rights
Connect
ERP, inventory, customer, finance
Configure
Journeys, controls, evidence
Pilot
Target site, data, adoption
Deploy
Network, support, improvement
Insights & resources
Go further.
Frequently asked questions
What to clarify before deployment.
01Can HERALD POS support several stores?+
The multi-site scope, synchronisation and degraded modes are confirmed against the target architecture.
02Are payments integrated?+
Terminals, providers, protocols and responsibilities are validated for each country and environment.
03Is the interface responsive?+
Yes. Devices, screen sizes, peripherals, roles and priority operations are still verified for each store environment.
04Can dashboards and reports be customised?+
Indicators, formulae, periods, axes, rights and output formats are defined with network managers.
05How is adoption prepared?+
Journeys, rights, control rules, devices, support and enablement are adapted to the selected roles and operations.
06SaaS or on-premise?+
Both deployment modes are available. The choice depends on the network, devices, connectivity, security and central systems.
Your next step
Build a fluid and controllable store experience.
Let’s discuss your stores, devices, payments, commercial rules and central systems.