Skip to content
Acceedo
Warehouse Stores

From an empty floor to a confirmed dispatch — one system.

Draw your warehouse, map every part to a rack cell, and let the floor run itself. Inspected stock is binned where it belongs, picked oldest-first, and routed to the operator step by step — with every movement logged and pushed back to your ERP.

6 stepsFloor design → dispatch
Strict FIFOOldest stock leaves first
Desktop + tabletQR scanning on the floor
Two-way ERP syncMovements and dispatches
How it works

Six steps, in the order the floor actually works

Nothing to configure in the abstract. Each step produces the data the next one needs — the floor you draw becomes the map the router walks, and the bin you place becomes the bin the picker is sent to.

Build the floor

Place racks, pillars and the entrance on a grid.

Map items

Assign each part the rack cells it lives in.

Inspected batches

Passed stock arrives with its inspection time.

Move to rack

Bin it, follow the route, drop it in the mapped cell.

Pick from rack

Load a slip, work the FIFO plan, deviate if needed.

Dispatch

Confirm, log the movement, sync to the ERP.

Floor builder

Draw the warehouse you already have

A click-to-place canvas, not a CAD tool. Set the grid to your real dimensions, pick a tool, click a cell. Racks, pillars and the entrance land where you put them, and the floor you draw is the map every route is later measured against.

Floor builder showing the Overflow Store floor: an 18 by 12 grid with six two-deep rack blocks separated by aisles, an entrance marked at E1, floor details and tool palette on the left.
Floor builder — three stores as tabs, six rack blocks laid out with aisles between them, entrance marked bottom-left.
  • Five tools, nothing to learn — select & drag, add rack, mark entrance, mark pillar, erase.
  • The grid is your building — set columns × rows, and every cell gets a coordinate like E1 or H10.
  • One entrance per floor, placed on the grid. Every pick route is measured from it.
  • Racks go down in pairs with aisles between them, so no rack is left without a face an operator can reach.
  • One tab per store — finished goods, dispatch staging, overflow — each with its own grid, entrance and racks.
  • Hold Space to pan, scroll to zoom, double-click to reset. Save the layout when it's right.
Item → rack mapping

Every part has an address

Pick a floor and a rack, then hand each part the block of cells it lives in. This one mapping is what makes everything after it automatic — the operator is never asked where something goes, and the picker is never sent hunting.

Item mapping for Rack B on the Finished Goods Store floor: all 16 cells mapped to three parts shown as coloured blocks spanning shelves S1 to S2, with a stat strip reading 16 total cells, 16 mapped, 0 empty, 3 items, and an All mapped items panel listing each part with its locations.
Item mapping — three parts holding Rack B between them, and every mapping in the warehouse listed alongside.
  • Blocks, not single cells — a part claims a rectangle like S1–S2 · C1–C2, so its home is a real bay you can point at.
  • Colour-coded per part, so who owns which stretch of a rack reads in one glance.
  • One part, several homes — the same item can hold space in finished goods and in dispatch staging at once, each with a jump-to link.
  • Occupancy on the header — total cells, mapped, empty, how many parts, and how full the rack is.
  • Import from Excel — map a whole warehouse in one pass instead of clicking it out rack by rack.
  • Everything downstream reads this — put-away routes target mapped cells, and the FIFO pick plan only ranks bins already in the right place.
Move to rack

Inspected stock, binned and put away

Three steps, in a fixed order: fill a bin from the inspected queue, follow the route the floor plan draws, and place it in the cell. The operator is never asked where something goes — the mapping already answered that.

  • Bin against what's actually left — each batch shows its balance as 490 − 100 = 390, not just the original quantity.
  • A bin belongs to one part — anything that would mix into it is locked out of the queue and says so.
  • Bins carry a type with a physical height and a capacity, so a bin can't be over-filled and the shelf maths later holds up.
  • One bin, several batches of the same part — each tracked separately, with its own batch number.
  • Age starts the moment it's filled — that timestamp is what FIFO ranks on when the stock is picked again.
  • See how full a column is before you lift — in the 3D view each candidate bay carries the height already used against the shelf's own.
  • Every placement is written to a ledger with its cell and time, and it is that record the ERP sync reads from.
Height strategy

The shelf decides what fits, not the operator

Bins stack vertically inside a rack cell. Before a bin is accepted, the app adds up the heights of everything already in that column and checks it against the shelf. If it will not fit, the placement is refused — on the screen, before the lift.

  • Height is a property of the bin type, so the maths is done from the master, not from memory.
  • Cumulative check against the cell's usable height on every single placement.
  • Clear rejection — the operator is told the column is full, not handed a silent failure.
  • Remaining capacity is queryable per column, so put-away can be planned rather than discovered.
Bin · 44 cm Bin · 34 cm Bin · 24 cm 56 cm free Bin · 74 cm Rejected 74 > 56 — won't fit
Placed bins Remaining shelf height Refused placement
FIFO & path to pick

The oldest stock leaves first — every time

Every bin remembers the inspection date of the oldest batch inside it. When a line is opened, the bins holding that part are ranked by that date and turned into a numbered plan: this cell, this bin, this many — in this order.

  • Every step names its cell — floor, rack, shelf, column and the cell code itself. There is nothing left to interpret.
  • Pick, available and age on each step — how many to take, what the bin actually holds, and how long it has been sitting there.
  • Ordered oldest first — the nine-day bin is step 1, the eight-day bin is step 2. Working the list top to bottom is FIFO.
  • Progress as you go — picked against required, what is left, and a percentage that moves with every pick.
  • Plan and Actual pick, side by side — what the system asked for, and what was really taken. Deviate when a bin is blocked; the audit keeps up.
The Pick Plan panel for item 1002, Impeller Casting 160 mm: 0 of 310 picked with 310 left, and two numbered steps in Rack A on floor FG01 — step 1 taking 111 from a bin aged 9 days, step 2 taking 199 from a bin aged 8 days.
The pick plan — oldest bin first, with the cell, the quantity and the age on every step.
Pick from rack

One slip, many lines, one confirmation

A pick slip carries as many item lines as the job needs. Load it on the desktop or scan the printed slip on a tablet, walk the route it draws, work the plan bin by bin, and confirm once at the end.

  • The whole job and the line you're on — a slip-level total like 100 / 1390 picked, and a bar per item beneath it.
  • Locked until you're actually there — the banner names the floor, rack, shelf and column, and Navigate takes you to it.
  • Scan the cell to unlock — picking opens only when the scanned cell is the one the plan sent you to.
  • Bins are colour-coded — recommended by FIFO, available, or holding another part entirely.
  • Take the suggestion, or don't — the quantity is pre-filled and one tap takes the lot; type a different figure when the bin won't give it up.
  • What you've already taken stays on the rack — bins picked on this visit grey back with the quantity marked, so nothing is counted twice.
  • Confirm dispatch once — every line closes together, the movement is logged, and the ERP push is queued.

QR everywhere it helps

Bin types, rack cells and pick slips all carry printable codes. The tablet camera reads the slip your ERP already prints — no relabelling project.

Desktop and tablet

Planning and masters on a desk; picking, binning and scanning on a tablet in the aisle. Same data, same second.

Two-way ERP sync

Inspected batches flow in; rack placements and confirmed dispatches flow back out — each on its own schedule, each with a run-by-run log you can open and read.

Dashboards

What moved, what is sitting still, and what changed

One period drives the whole board, and every headline carries the period before it — space and ageing, what shipped and when the floor was busy, then every part ranked and any handful of them plotted against each other.

Every figure has a yesterday

Each headline carries the previous period beside it and the gap between them, so a number is never presented without the context that makes it good or bad news.

Turns and cover, per part

How many times a part's stock turns over in a month, and how many days of cover is sitting there — which is what tells you a slow mover from a dead one.

When the work happens

Movements by day and by hour of the week, so the shift pattern the floor actually runs is visible rather than assumed.

Per-operator activity

Placements, picks, undos and cells touched, per store keeper — read straight off the movement ledger rather than a separate tally.

Cards or list, and a search

The item board switches layout and narrows to a single part without losing the period you set — cards for a wall display, a list for the long tail.

Trends you assemble

Pin several parts onto one chart to compare them directly, or hold a single part against its own previous period. Both read cumulatively, so the shape shows when the work actually happened.

Dispatch reports

A month of dispatch, two ways to read it

Pick a part and a month. See it as a calendar when you care about one item day by day, or flip to the matrix when you need every item across the whole range at once.

Calendar view

One part, one month, one cell per day: quantity dispatched, the change against the day before, and how many slips it took. The month total sits on top with last month beside it.

  • The month in one line — total dispatched, the month before, the percentage between them, active days against last month's, and total slips.
  • Every day carries three figures — quantity, the change on the previous day, and how many pick slips produced it.
  • The 1st is not a blank — it compares against the last day of the previous month, and the footer names that date and its quantity outright.
  • “first” instead of a false zero — when nothing shipped the day before, the cell says so rather than inventing a percentage.
The dispatch calendar for part 1014, Water Pump Body, July 2026: 6,010 dispatched against 3,080 in June — up 95.1 percent — across 10 active days and 13 slips, with each day cell showing its quantity, its change on the day before, and its slip count.
Calendar view — one part across a month, each day measured against the one before it.

Matrix view

Every part down the side, every day across the top, ranked by volume. Switch the range to weeks or months and the columns follow — the identity and the totals stay pinned while the dates scroll under them.

  • Day, week or month columns from one control — the header tells you which you are looking at.
  • Four pinned columns — part number and description on the left, total and slip count on the right, while the dates scroll between them.
  • Ranked by volume, so the parts that move most are the first thing you read.
  • Volume and transaction count together — 3,070 units over 7 slips is a very different month from 3,011 over 13, and the two sit one row apart.
The dispatch matrix for July 2026: 60,401 dispatched across 20 items and 172 slips, with part number and description pinned on the left, one column per day scrolling in the middle, and total and slip count pinned on the right.
Matrix view — every part against every day in the range, ranked by total.

Excel export, generated server-side

The calendar exports two sheets — one row per day, plus every individual movement with its slip, batch and quantity. The matrix exports exactly what is on screen, range and all.

Movement-level traceability

Every figure drills down to the pick slips and batches that produced it. A number on a report is never the end of the trail.

Sync logs you can open

Dispatch and rack-movement pushes to the ERP are logged run by run, split into what landed and what failed, with a manual re-run button.

At a glance

The short version

Floor designMulti-floor, grid-based. Racks, pillars and a single entrance per floor. Configurable rack columns, rows and direction.
LocationsCell-level addressing per rack. Items mapped to one or many cells, across one or many racks.
Stock unitBins. Each carries a bin type with a colour and a physical height, and can hold multiple inspected batches.
Put-away rulesVertical stacking within a cell, validated against cumulative bin height versus usable shelf height.
Picking ruleStrict FIFO by inspection date of the oldest batch in each bin. Deviations permitted and recorded.
RoutingGrid pathfinding from the operator's position to the target cell, computed off the main thread.
SlipsMulti-line pick slips. Created from the desktop master or by scanning the printed slip's QR on a tablet.
ScanningBin-type QR, rack-cell QR and pick-slip QR. Rack-cell scan gates the pick to the correct bay.
Rack viewsEvery rack opens as a 3D isometric figure or as a compact card grid, on one toggle — the same pair in item search, in put-away and at the pick face.
Stock visibilityWarehouse-wide item search by number or description, drilling floors → floor → rack, with per-bay hover detail and per-cell drill-down.
ReportingItem movement dashboard, dispatch calendar and item×period matrix. Server-side Excel export on both report layouts.
IntegrationInspected batches pulled from the ERP; rack placements and confirmed dispatches pushed back, with retry and per-run audit logs.
DeploymentBrowser-based, multi-tenant. Tablet operation runs in the same app through a native camera bridge.

See it running on your floor plan

Send us a sketch of your warehouse and a handful of part numbers. We will build the floor, map the items and walk you through a full put-away and dispatch on your own data.

Typically a 30-minute session. No installation required.