Back to Refract Spaces Demo · POS product import Sample data — nothing real

POS product import and receiving — Refract Spaces demo

  1. 1Purchase order
  2. 2Map columns
  3. 3Review
  4. 4Receive

Import a purchase order

Suppliers send whatever their system exports. Column names differ, the order differs, and half the time the file has a header row nobody asked for. The import has to cope with that without anyone retyping 14 lines into a point-of-sale terminal.

PO-4417_northline.csv —

What the supplier actually sent — first six lines, unedited:

—
The file is pre-attached so you can walk the flow. In the real build this is a drag-and-drop, an email inbox, or a supplier feed — the three steps after it are identical either way.

Confirm the column mapping

We guessed from the header names. Guesses are shown as suggestions, not facts — anything we weren't confident about is left for you, because a silently wrong mapping is far more expensive than a question.

What we found

Everything importable is imported. Everything questionable is surfaced now, while it is still cheap to fix — not discovered three weeks later by someone scanning a shelf.

Mapped result

The first eight lines, as they will land in the catalogue.

Receive the delivery

The pallet is open and someone is counting. Expected quantities come from the PO; anything that doesn't match gets flagged and needs a reason before the receipt closes.

Lines counted0 / 0 Units received0 Variances0 Received value$0

Receipt closed

—

In the live system this is the moment stock becomes sellable, the short line opens a supplier claim, and the cost basis lands on the product record. One person, one counter, about four minutes.