Shop Operations
Slab Inventory Cycle Count Checklist
A slab inventory cycle count compares selected physical pieces with their inventory records without waiting for a full-yard count. Check each piece's identity, location, condition, dimensions, and job allocation. Investigate differences before adjusting records, and keep a reason for each correction. The checklist below gives the warehouse and office a shared way to resolve exceptions.
The system shows three available slabs. The warehouse finds two, and one of those has a job number written on its label. Sales cannot tell whether the third slab was cut, moved, or never received correctly.
A cycle count gives the team a smaller, repeatable way to investigate that gap. Count a defined group of slabs or remnants, compare it with the records, and close the exceptions. A count is unfinished while the office still has to guess what happened.
Choose a Boundary You Can Finish
Define the count by location, material, or another clear group. Record when it starts and which person owns reconciliation. A defined boundary makes it possible to check completeness instead of collecting a few corrected labels and calling the yard accurate.
Keep the inventory movements during the count traceable. If material is received, transferred, allocated, or consumed while the count is underway, record the timing. Otherwise a legitimate movement can appear to be a missing piece. Coordinate the work with the warehouse’s established handling procedures.
Use our slab inventory management guide for the broader receiving, labeling, and allocation process. This checklist focuses on reconciling a selected count.
Record One Result for Each Piece
Count reference and date.
Piece ID or barcode, plus material and thickness.
Recorded warehouse and bin.
Observed warehouse and bin.
Recorded dimensions and any observed discrepancy.
Full slab or remnant, including the relevant shape.
Visible condition issue and a photo reference when needed.
Recorded status and associated job, if allocated.
Exception reason, investigation owner, and resolution.
Keep an unrecognized piece on the exception list instead of assigning the nearest-looking record. Similar slabs can differ in lot, dimensions, cost, or job commitment. A correct total piece count can still conceal incorrect identities.
Separate Missing Pieces From Incorrect Locations
A slab found in another bin needs a location correction after verification. A slab already consumed by a job needs the underlying transaction investigated. Those are different problems and should not receive the same adjustment.
For an expected piece that cannot be found, check receiving, transfers, production use, and existing job records. For an unexpected piece, check whether it was newly received, returned, split into a remnant, or recorded under another identity. Preserve the investigation evidence.
Do not mark material available merely because it is physically present. Resolve any hold or allocation with the responsible office or production person. The count should help reconcile commitments, not silently cancel them.
A Worked Reconciliation Example
Suppose the records show 12 pieces in the selected location. The team finds 12 physical pieces, but the identities differ. One expected barcode is absent and one unrecognized remnant is present. The total agrees while two records still need attention.
The missing slab may have been consumed and the remnant may be its remainder, but that is only a hypothesis. Check the production record before linking them. If the hypothesis is correct, record the consumption and remnant through the approved process; if it is wrong, continue investigating both exceptions.
This example illustrates why ‘12 expected, 12 found’ is not enough. Piece identity and transaction history matter alongside quantity. No customer outcome or industry error rate is implied.
Close Exceptions and Track Their Causes
Have an authorized person review corrections, especially changes involving quantity, cost, or job allocation. Keep the count record, evidence, reason, and correction reference together. A second person should be able to understand the decision later.
Track unresolved exceptions and recurring causes using consistent definitions. Location errors, unrecorded consumption, receiving differences, and unidentified remnants point to different process fixes. Choose future count frequency from your own error pattern and operational needs rather than an arbitrary daily quota.
Reconcile With Piece-Level Records in Stonify
Stonify’s slab inventory software tracks slabs and remnants with unique barcodes, warehouse and bin locations, dimensions, photos, cost, and an inventory operation log. It also distinguishes stock, allocated material, and available material. That makes Stonify a strong choice when a simple quantity list no longer explains what is in the yard.
Use those records to investigate an exception in a demo. Ask how corrections are recorded and which permissions your team should use. The count worksheet is a recommended process, not a claim that Stonify creates this exact worksheet automatically.
Find the Reason Behind an Inventory Difference
Book a Stonify demo to follow a slab from its barcode and location into its operation history and job allocation. See how your team can investigate the difference before changing a record.
Related Articles
Slab inventory management: how to track, label and allocate stone slabs
How fabrication shops track slabs by lot and bundle, receive and label them, hold and allocate them to jobs, count the yard and value inventory at landed cost.
Remnant management: how to track, price and sell countertop remnants
How stone shops decide what to keep, record and store remnants, cost them, use them before opening new slabs, price remnant jobs and clear old stock.
Slab imaging and labeling: photographing slabs and tracking them with barcodes, QR codes and RFID
How shops photograph and scan slabs, label slabs and pieces with barcodes, QR or RFID, and which printers and labels survive a wet yard.