RETAIL
Monday’s decisions, not last Monday’s numbers.
Gloree holds store, SKU and shipment data from NetSuite, SAP and Salesforce in one live grid, so the trading pack is built on the week that just closed.
The week does not wait for the close.
The rhythm is weekly. The ledger is monthly.
Buying, allocation and markdown calls are made every Monday against figures assembled for a monthly close. The pack is rebuilt each week from exports that were never meant to be pulled that often.
Volume is the problem, not the arithmetic.
Hundreds of stores, tens of thousands of SKUs, several currencies and a promotional calendar that moves the comparison every fortnight. None of it fits on a screen, and refreshing it costs an afternoon.
Seasonality punishes a lazy comparison.
Week 47 against week 46 says nothing. Week 47 against the same week last year, restated for the stores that were not trading then, is the number the buyer needs and the slowest one to produce.
Workflows
The trading pack builds itself.
Schedule the pull, the recalculation and the Slack post for six on Monday morning. The pack in the buying meeting was built from the week that closed hours earlier, and the run is on record.
The systems a retail finance and merchandising team already report out of
Stores and regions in one workbook.
Entities, currencies and store groups sit on sheets that share one set of connections, so a regional total and a single store line come from the same refresh.
Refreshed, not rebuilt.
Next week’s pack is this week’s pack with new figures in it. The layout, the formulas and last week’s commentary all survive the update.
Variance held at the line, not the total.
Shipment and sales variance stays at the level the decision is taken at, rather than being summed into a total that hides which SKU moved.
Not every close is weekly.
Banking files to dates a regulator sets, then defends each figure years afterwards. Oil and petrochemicals publishes numbers a joint-venture partner re-audits line by line. Same grid, different pressure.