Check the figures before a store decision
A product can sell out at one store while sitting on the shelf at another. Before restocking, discounting or moving it, your team needs current sales, stock, reservations and deliveries. Omni can bring those records together and show what still needs checking.
Start with an agreed decision rule and a defined reporting period. A low sales figure may reflect missing data, reduced opening hours or stock that was unavailable. A useful exception report distinguishes those possibilities rather than labelling every decline a demand problem.
Work with POS, inventory and allocation tools
Your current software may already suggest stock moves, send alerts or handle approvals. Check those features first. Additional work is useful when someone still has to match exports, store notes or warehouse records by hand.
| Record | What needs to match |
|---|---|
| POS sales | Store, product, variant, date range, returns and cancellations. |
| Inventory snapshot | Available, reserved and in-transit stock, with a timestamp. |
| Warehouse record | The same product and unit definitions as the store records. |
| Transfer history | Requested, approved, dispatched and received quantities. |
| Store observations | A dated note linked to the correct store and product. |
How Omni can work with current software shows one way to bring these records together. A new review will not automatically improve your current stock suggestions or replace them.
Prepare a transfer review and trading report
For example, one store has sold out of a jacket size while another has several left. Omni can show both stores' records, warehouse stock and limits on moving stock. Sales history alone is not enough to decide how many to move.
Identify the exception
Use the agreed store and product rules on a dated dataset.
Check availability
Reconcile reserved stock, in-transit items and the latest relevant observations.
Prepare the review
Show the source records, calculated figures and questions for the merchandising team.
Decide
The authorised manager confirms whether to transfer, change the proposal or take no action.
A weekly trading report can summarise the same records by store and category, distinguishing proposed actions from completed transfers or markdowns. Use consistent measures and periods. Missing product-category mappings should remain visible, rather than being silently assigned or excluded from totals without explanation.
When weather or season matters
Season calendars and weather information may help a merchandiser interpret a pattern, but they do not prove its cause. Include an external source only when it is relevant, licensed for the intended use and sufficiently current. State the date and distinguish a forecast from an observed condition.
For a first test, sales and stock records may be enough. Add weather or other information only if it helps the team understand the figures. Promotions, missing stock and other changes still need to be considered.
Define review and action responsibilities
Agree who can see each store's records and approve stock moves, discounts or purchases. A first test can prepare a review without changing stock or prices. Any later system update needs confirmed permissions and checks for changed, rejected or repeated requests.
The record of a review should identify its source snapshot, output version and decision. An approval based on yesterday's available stock may no longer be valid after a reservation. These are implementation checks to settle with merchandising, operations and IT; see security and governance.
Questions retail chains ask
Our POS and ERP use different product codes. Can we still start?
First match the product codes or agree how staff will resolve uncertain matches. Similar product names are not enough to combine records safely. Fixing those codes may be the best first task.
Will it automatically change prices?
The examples here prepare information for a merchandiser. Price changes and transfers are separate actions that require explicit scope, authority and tested controls.
How do we tell whether it helps?
Check record matching, missed exceptions, false alarms and the effort needed to prepare and review the output. Any claim about sales or stock reduction requires additional operational evidence.
Which region should we use first?
Choose a manageable set of stores with representative records and an available reviewer. Include a missing export and a changed stock position, not only clean examples.
Can we see an example output?
The homepage examples show sample screens and made-up figures. Use them to discuss what a useful store review should show.
Talk through your taskTell us where store, stock and trading records need to come together for a decision.