Serialized Inventory, QR-Traced: Tracking Every Unit From Dock to Shipment

Ask most monument and stone wholesalers how many of a given product they have. The usual answer is a range. Spreadsheets conflict with operations, and neither accounts for the units already promised to pending orders. When inventory lives as a single figure, that figure is almost always wrong when you need it.

Stone inventory makes the problem harder as units are heavy and expensive. A polished upright is not interchangeable with the one beside it, the way a box of screws is. So the important question is not how many you have, but which specific units you can commit to this order, and where those units are located.

Stonegate Scribe is built to answer that question. Every physical unit becomes a tracked record. Each record is organized by SKU, placed in a location, moved through a state lifecycle, and tied to a QR label that anyone on the floor can scan to see its full history. What follows walks through how the system does this, from the dock to the customer.

Stock by SKU

Everything starts with the SKU, the description of a stockable product. Each SKU records what the thing is, whether it is a finished good or a raw blank, its physical dimensions and weight, and a minimum or reorder quantity that sets the threshold for low-stock alerts. SKUs can be searched, looked up by their options, and linked to orders.

What sits beneath each SKU is more important. Inventory levels are tracked per SKU and per location, giving operational teams confidence in their stock. The system separates the states into:

• On hand. Physically present and free to sell.
• Allocated. Present, but already committed to an order.
• Damaged. Present, but not sellable.
• In transit. Inbound, not yet received.
• In-transit allocated. Inbound and already spoken for.

This split answers the most important quoting question for your customers: is this SKU in stock? Restocking a product that is out of stock can take days to months, and that delay can affect what your retailers purchase. A customer-visible flag on each SKU controls whether it surfaces in customer-facing availability. A dedicated low-stock view flags any SKU that has dropped under its reorder threshold, so replenishment is something you see coming rather than discover at fulfillment.

Every Unit Is a Serialized Record

Below the SKU, each physical unit is a serial with its own record. It knows its current location and its source lineage: which receipt or purchase order created it, and which allocation currently owns it. That lineage is what makes a unit traceable rather than merely countable.

Each serial moves through a defined lifecycle. The main states are In Transit, On Hand, Allocated, and Shipped, with Damaged and Consumed as side states for units that break or get used in production. The states are color-coded everywhere they appear in the interface. Floor staff can read a unit's status at a glance instead of cross-referencing a status code.

Typed Locations

Inventory sits in a hierarchical tree of locations. Locations can nest under one another and are typed by purpose: warehouse, storage, damaged, staging, receiving dock, shipping dock, and work-in-progress. Each location carries full address fields, which means the same record that organizes your warehouse also doubles as a ship-from or receive-to point. A unit's location is never an afterthought. It is part of the record, and it changes as the unit moves.

Sales Allocations Bind Stock to Orders

Allocations connect inventory to the orders that need it. An allocation links a specific order line item to a specific serial, along with quantity and status. If the stock has not arrived yet, the line can be allocated against a purchase-order line instead. Demand can be committed to inbound units before they reach the dock.

Allocations can be created per order or in bulk, and a release action frees committed stock when an order changes or falls through. Tying it together is an inventory needs report. For every open order line, that report shows quantity ordered against quantity allocated against quantity still pending. It is the fulfillment worklist. Your team can see exactly what still needs stock and how much.

Serials Start at Receiving

Receiving a purchase order is where serials come into existence. PO lines track quantities ordered, received, damaged, missing, and allocated. When you receive a line, the platform mints serialized units for the received and damaged counts. It then offers to print QR labels for what just arrived, with received and damaged units grouped separately. The purchase order itself moves through its own status flow as goods come in, from draft to submitted to acknowledged to partially received to fully received.

The practical effect is that labeling is not a separate chore you have to remember. A unit is created and labeled in the same step it is received. That step is the only point where the digital record and the physical object are guaranteed to be in the same place at the same time.

An Immutable Trail Behind Every Move

Every state change and every location change is recorded as a stock movement that cannot be edited after the fact. Each movement captures the serial, the from and to locations, the from and to states, and a reason: receive, transfer, allocate, deallocate, damage, consume, produce, ship, or adjust. It also captures a reference to whatever drove the move, whether a purchase order, shipment, work order, sales allocation, or manual entry, along with the actor who did it, the timestamp, and a free-text note.

Read end to end, those movements are the trace. For any unit you can reconstruct every hop from the receiving dock to the customer's shipment, with who did it, why, and when attached to each step. When a question comes up about a specific piece, the answer is a record rather than a recollection.

QR, From the Dock to the Customer

QR codes link the digital record to the physical object. Every serial encodes to a QR code, and labels can be printed in batches. Printing uses the browser's print pipeline with format-specific layouts rather than a proprietary printer driver.

Scanning works from either a USB or keyboard-wedge scanner gun or a live camera, so the floor can use whatever hardware it already has. A scan resolves whether the input is a bare serial token or a full unit URL, then jumps straight to that unit's detail page and its movement history. A unit gets its label at receiving. From that point on, anyone can scan it to pull up its identity, current state, location, and complete trail.

Shipments and Fulfillment

Shipments move allocated stock out, and follow a state machine rather than a status field that someone updates by hand. A shipment can be outbound to a customer or an internal transfer between your own locations. It progresses through allocating, ready for release, released, in production, shipped, arrived, and closed. Shipment types carry transport mode and capacity limits, with maximum weight and quantity enforced as you allocate orders, and a utilization bar shows how full a shipment is. When it is time to move freight, the platform generates a Bill of Lading with the customer and freight-terms details ready to download.

One System, From Receipt to Shipment

The thread running through all of this is that a unit is never just a tally mark. It is a record that knows what it is, where it is, what state it is in, which order owns it, and everything that has happened to it. Stock is tracked by SKU with a true on-hand, allocated, and available split. Each physical unit is a serialized record moving through a defined lifecycle. Units bind to orders through allocations, get labeled with a QR code at receiving, and stay traceable by scan from the receiving dock to the customer's shipment.

For a business where the inventory is heavy, valuable, and one of a kind, the precision has a clear payoff. It is the difference between having confidence in your inventory and hoping the spreadsheet was right.