Cybex Retail AI
Cybex Retail Stack · Transformation

BI and AI Retail Transformation

Six connected workflows take a fashion retailer from last season's results to next season's buy, then to the shelf, the books and back again. One data platform, one set of numbers. Automation and Optimization.

AssortmentMerchandising & ReplenishmentWMS AllocationMarkdownSales AuditBI & AI Analytics
Fashion buyers reviewing the range and seasonal calendar on screen in the sample room, with rails and fabrics behind

One season, six workflows

Most retailers run these as separate departments with separate spreadsheets, so every hand-off means re-keying. On the Cybex Retail Data Platform each workflow starts from the previous one's output. Last season's results set this season's buy, and this season's results feed the next review.

  1. 1AI Assortment PlanningWhat worked last season, and what should we buy next?
  2. 2AI Merchandising & ReplenishmentPlan, buy, publish, receive, reorder.
  3. 3AI WMS AllocationThe right units in the right store and size.
  4. 4Markdown OptimizationMark down on purpose, not by the calendar.
  5. 5AI Sales Audit & AccountingEvery sale, tender and invoice reconciled.
  6. 6BI & AI Operations AnalyticsRun the business on one set of numbers.
Cybex Retail Data Platform · sales, stock, orders, receipts, payments and plans, loaded and reconciled every nightResults from step 6 feed step 1 of the next season

Automated runs without anyone touching it   AI the system recommends, a person approves   Decision a person decides with the data in front of them   BI reporting and monitoring

1
Workflow 1 · AI Assortment Planning

Score last season, then plan the next

When 8 to 10 weeks before the buy, e.g. S25 and S26 reviewed in the autumn for S27Who merchants, buyers, plannersOutput the assortment brief for the buy meeting
#StepCybexMode
1Load and reconcileSales, receipts, stock, orders and returns to vendor loaded nightly. The stock ledger is balanced to on hand before anything is analysed.Data PlatformAutomated
2Season scorecardThis season against last: sales, gross margin, markdown rate and full-price sell-through by season code, department, class, brand and style-colour.AI Insights: Season ReviewAI
3Breadth and depthOptions per class, units per option, and the tail of style-colours that sold one unit or none.AI InsightsAI
4Older stock and margin leaksWhat carried over from earlier seasons, what it sold at, and which departments lost margin.AI InsightsAI
5White spaceClass by price band cells where sell-through and productivity say add options, and cells that carry more options than sales.AI InsightsAI
6Brands to back, brands to cutSell-through, sales per option and what is already on order for each brand.AI InsightsAI
7Size curvesReceipts and sales by size family, and sizes bought one unit deep.AI InsightsAI
8The buy gapNext season's orders against the same date last year, the units needed at a target sell-through, and how much buy is left.AI InsightsAI
9Assortment briefA written summary for the buy meeting: where to add, where to cut, which brands, which sizes, how much is left to buy.Executive reportDecision

Efficiency

A full season review in hours rather than weeks of spreadsheets, built the same way every season.

Optimization

Fewer, deeper options. The buy is sized to a sell-through target instead of last year plus a percentage.

Automation

The dataset recalculates every night. The live view and the executive report come from the same numbers.

Example (anonymised specialty apparel retailer). The spring buy had 11% fewer units, yet new-season sales rose 12%. Sell-through went from 56% to 63%, and stock left at season end fell by a third. The same review showed next season's orders already 24% ahead of the same date last year, so the rest of the buy was capped before last year's late orders could repeat.
Hands off to workflow 2: option and depth targets by class, the brand list, size curves and the open-to-buy left for the season.
2
Workflow 2 · AI-Powered Merchandising & Replenishment

Plan, buy, publish, receive, reorder

When the buy period, then weekly in seasonWho planners, buyers, product and e-commerce team, receiversOutput purchase orders inside open-to-buy, product live in store and online
#StepCybexMode
1New season merchandise planSales, stock-to-sales and markdown % by class and month, started from last year and the season review instead of a blank sheet.Merchandise Plan: New PlanAI
2Open-to-buyOn order is refreshed every night from the purchase orders, so OTB by class and month is always current.Merchandise Plan: OTBAutomated
3Order workbenchLast season's winners to rebuy, new styles matched to the style they replace, size curves applied, draft POs built inside OTB.Merch Plan Style: Order WorkbenchAI
4Create new productStyles, colours and size SKUs generated from the size table, with attributes, prices and prints on blanks.Product maintenanceAutomated
5Approve and issueDraft POs reviewed and released to vendors as purchase orders.PurchasingDecision
6Publish to e-commerceProduct, variants, prices and status published to Shopify from the same product master, so nothing is keyed twice.Shopify publishAutomated
7ReceiveReceipt scanned against the PO, price tickets and GS1-128 labels printed, over, short and substitutions flagged on the spot.Receiving and ticketingAutomated
8In-season opportunitiesReorders and chases on winners from the forecast (six-week base and weeks of cover), plus direct-to-store buys.Suggest PO, Direct-to-StoreAI

Efficiency

Plan, OTB, POs, product and the online store come from one product master. Product is set up once.

Optimization

Every PO is checked against open-to-buy and the season review. Winners get chased while there is still season left.

Automation

Nightly on-order, generated SKUs, one-click publishing to Shopify, labels at receiving.

Hands off: received stock goes to workflow 3; receipts and PO costs go to the invoice match in workflow 5; on order goes back into the plan.
3
Workflow 3 · AI-Powered WMS Allocation

The right units in the right store and size

When on every DC receipt, then weeklyWho allocators, DC team, store operationsOutput stores stocked to their demand, sizes kept together
#StepCybexMode
1Initial allocationEach DC receipt split by store from the store's forecast need, 1 to 8 weeks of cover, by size.AI AllocationAI
2Pick, pack and labelPick lists, box counts and carton labels generated from the allocation.WMS, shippingAutomated
3Ship and receive at storeTransfers sent and confirmed at the store, so stock in transit is never lost between systems.WMS, POSAutomated
4Replenish from the DCUnits sold are replaced from DC stock each week, up to each store's cover target.ReplenishmentAutomated
5Re-allocate between storesWhen the DC is out, slow stores give to stores that sell, by size.Re-allocationAI
6Consolidate before markdownBroken size runs gathered into fewer stores, so they sell before they need a markdown.Re-allocationDecision
7DC productivityUnits in and out, flow by day, open allocations.DC analyticsBI

Efficiency

Allocators review exceptions instead of building every allocation by hand.

Optimization

Stock follows demand by store and size, which means fewer lost sales in some stores and fewer markdowns in others.

Automation

Allocation, pick lists, labels and weekly replenishment run from the same forecast.

Hands off to workflow 4: stock and weeks of cover by store and size, and size runs that are already broken.
4
Workflow 4 · Markdown Optimization

Mark down on purpose, not by the calendar

When weekly from mid-seasonWho merchants, planners, financeOutput price changes with a reason, and margin protected
#StepCybexMode
1Where each style standsSell-through against plan, weeks of cover, and weeks since first receipt, by style-colour.AI InsightsAI
2CandidatesSlow sellers, broken size runs and older season codes, ranked by retail value at risk.AI InsightsAI
3Timing and depthAn early, shallow markdown against a late, deep one, compared by class on margin dollars.Markdown modelDecision
4Price changeOne approved change sent to POS and e-commerce together.Price change, ShopifyAutomated
5MeasureLift, margin dollars and markdown rate against plan, week by week.BIBI
6Feed the planActual markdown % returns to the merchandise plan and next season's review.Merchandise PlanAutomated

Efficiency

One weekly list instead of a store walk and a spreadsheet.

Optimization

Markdowns go where they move units, so more of the season sells at full price.

Automation

Approved prices reach the stores and the website together, and results are measured on their own.

Why it matters. In the anonymised season review above, gross margin fell 6 points while new-season product held its margin. The loss came from older stock sold at deep discounts. A weekly markdown workflow finds that stock while it can still sell at a shallow discount.
Hands off: markdown cost and clearance results go to workflow 5 (inventory at cost) and workflow 6 (margin analytics).
5
Workflow 5 · AI Sales Audit & Accounting

Every sale, tender and invoice reconciled

When every day, and at month endWho sales audit, accounts payable, controllerOutput a balanced GL journal, and only the exceptions left for people
#StepCybexMode
1Daily closeStore and web orders loaded and balanced: tickets, tenders, taxes and returns.Sales AuditAutomated
2Card matchProcessor settlement matched to POS payments by store, register and invoice.Card reconciliationAutomated
3Exceptions explainedTerminal logs read for every unmatched payment: lost terminal reply, rung twice, approved but not settled, partial approval.AI Sales AuditAI
4DepositsCash and card deposits balanced to the bank.Deposit balancingAutomated
5Receipt, PO and invoice matchVendor invoice checked against PO cost and received quantity, within tolerances. Only the differences go to AP.Three-way matchAutomated
6Inventory at costStock ledger at moving average cost: receipts, transfers, adjustments, shrink and markdowns for any period.Stock ledgerAutomated
7GL journalSales, tenders, cost of sales, inventory and payables posted to the ERP, such as Business Central.GL journalAutomated

Efficiency

Auditors and AP clerks work the exception list, not every transaction.

Optimization

Lost card payments, duplicate charges and vendor overbilling are caught within days, not at year end.

Automation

Daily matching, deposits, the stock ledger and the GL journal run every night.

Example (anonymised multi-store retailer). In one month, 99.69% of 49,601 card payments matched automatically. Each of the 152 exceptions came with its cause from the terminal logs.
Hands off to workflow 6: audited sales, margin at cost and clean payment data, the same numbers finance reports.
6
Workflow 6 · BI & AI Operations Analytics

Run the business on one set of numbers

When every morning, and at weekly and monthly reviewsWho executives, store and district managers, merchants, financeOutput decisions, and the input to next season's review
#StepCybexMode
1Store operationsTraffic, conversion, average ticket, units per transaction and sales by associate, daily and weekly.BI templatesBI
2Merchandise analyticsSell-through, cover, aged stock, and size and brand matrices for any period.BI Query and MatrixBI
3AI InsightsFindings and actions in plain language, generated from governed datasets, with the data behind every number.AI InsightsAI
4Exceptions to ownersAudit, stock and plan variances sent to the person who acts on them.AlertsAutomated
5AI data warehouseEach insight's dataset stored by season, building the history that later models learn from.AI data warehouseAutomated
6Close the loopThe season's results become step 1 of the next season review.All six workflowsDecision

Efficiency

No month-end report builds. Every role opens the same numbers each morning.

Optimization

Store, merchandise and finance results side by side, so the cause of a problem shows up, not just the symptom.

Automation

Datasets, insights and alerts refresh overnight, and nobody has to export anything.

Back-office automation: from purchase order to general ledger

The biggest efficiency gain is the paperwork between the workflows. One product master and one transaction record carry each unit from the order to the books, with no re-keying.

  1. Purchase orderBuilt in the workbench, inside OTBWorkflow 2
  2. ReceiptScanned against the PO, over and short flaggedWorkflow 2
  3. Merchandise handlingTickets, GS1-128 labels, cartonsWorkflows 2 and 3
  4. Allocation and transferDC to store, store to storeWorkflow 3
  5. Invoice matchInvoice vs PO cost vs received quantityWorkflow 5
  6. Inventory at costMoving average stock ledgerWorkflow 5
  7. GL journalPosted to the ERP, balancedWorkflow 5

Technology adoption: five stages, each paying for the next

Retailers don't need to switch everything on at once. Each stage of the Cybex Retail Stack runs on the data you already have, and each one delivers results before the next begins.

Stage 1 · Data

One reconciled dataset

Connect POS, e-commerce, ERP and WMS to the Cybex Retail Data Platform on your existing data warehouse. Balance sales and stock to the books.

Stage 2 · BI

One set of numbers

BI templates for stores, merchandise and audit replace exported spreadsheets. Everyone reads the same figures every morning.

Stage 3 · AI

Insights with actions

Start with a season review for the next buy. It shows value inside one buying cycle.

Stage 4 · Automation

Remove the re-keying

OTB, product publishing, receiving, card matching, invoice matching and the GL journal run on their own.

Stage 5 · Results

Optimize to targets

The buy, allocation and markdowns are set against sell-through, cover and margin targets, and measured every season.

How each role changes

RoleTodayWith the six workflows
PlannerBuilds the plan in spreadsheets from exported reportsStarts from last year and the season review. OTB is current every morning
BuyerPrepares line reviews by handWorks from winners, white space, brand scores and draft POs in the workbench
Product and e-commerceKeys product into the POS and again into the online storeCreates product once and publishes it to Shopify from the same master
Allocator and DCSplits receipts by hand and reacts to store callsReviews AI allocations and re-allocations; labels and pick lists are generated
Sales audit and APTicks and ties every tender and invoiceWorks only the exception list, each exception with its likely cause
FinanceWaits for month end, then reconcilesReceives a balanced daily journal and inventory at cost for any period
ExecutiveReads a monthly deckReads nightly insights with the actions that go with them

The scorecard

Workflow 1Full-price sell-throughSeason stock sold before markdown
Workflow 1Options selling one unit or noneThe tail of the assortment
Workflow 2Receipt to selling floorDays from the dock to the floor and online
Workflow 3Weeks of cover by storeStock where demand is
Workflow 4Markdown rate and GM%Margin kept on the season
Workflow 5Auto-match rateCard payments and invoices matched without a person
Workflow 5Days to closeMonth end to a balanced ledger
Workflow 6One version of the numbersReports built by hand each month
Next Step

Start with one season review. Grow into all six workflows.

We pilot on your existing data warehouse: last season scored for next season's buy, in your own numbers, in a few weeks.