Skip to main content
Warehouse Management

Every box accounted for,
from the dock to the truck

QC-WMS keeps a live account of what arrived, where it is standing, what condition it is in, what has been promised to a customer and what has left the building. Every change of state happens through a scan, and every scan is checked against a rule before it is allowed.

Request a demo
See how it works
5
picking stages, from import to shipped
22
reports, every one exportable
4
tracked levels: shelf, pallet, box, part
See the modules

QC-WMS is a warehouse management system for manufacturers, built by Share IT Smart (Arad, Romania). It tracks stock at four levels - shelf, pallet, box and part - and enforces the rules of the warehouse at the moment of the scan rather than reporting the breach afterwards.

QC-WMS is not an ERP and does not hold your financials. It is not a transport management system - that is QCLOT, which prices and books the freight that leaves your dock. It does not schedule production, and it is not a quality traceability system in the sense that BatchTrace or TML are.

Your Challenges

The stock on the report is not the stock on the floor

Almost every complaint a warehouse manager fields has the same root: a movement that happened without a record, or a number that means something different from what the person reading it assumed.

Movements that leave no trace

A pallet gets moved, a box gets taken for a trial, material goes to the line without paperwork. The count drifts, and by the time the annual inventory finds it nobody can reconstruct what happened.

Today's picker empties tomorrow's delivery

Two customers need the same part this week. Whoever picks first takes what they need, and the earlier delivery discovers on the loading dock that its stock is gone.

Two people read the same number differently

Stock on hand, available stock, blocked stock and staged stock are four different figures. When a report says one thing and the shelf says another, the argument is usually about which of the four was meant.

Quality holds live in email

A batch is put on hold verbally or in a spreadsheet. Nothing physically stops an operator picking it, and nobody can produce a list of what is currently held and why.

Our Approach

Rules enforced at the scan, not audited afterwards

The system refuses the movement that would break the count, at the moment someone tries to make it.

Pillar 1

Every state change is a scan

Receiving, building a pallet, putting it away, issuing to a line, picking, validating, shipping and counting all happen by scanning a code. There is no screen where a quantity is simply typed over.

Pillar 2

Four levels, one status model

Shelf, pallet, box and part. Each pallet carries one status from a fixed set, and that status alone decides whether its stock is available, pickable, reportable and movable.

Pillar 3

What you have and what you can promise are different numbers

Gross quantity is everything physically on the pallet. Available quantity is gross minus what is already allocated to a delivery. The system keeps them apart everywhere, which is what makes the availability guard possible.

The distinctive thing about QC-WMS is not that it records the warehouse. It is that it refuses movements that would make the record wrong, using rules a manager can read and explain to the operator who just got blocked.

Feature 01 - Outbound

Five picking stages, and a guard that protects earlier deliveries

A customer delivery plan is imported from a spreadsheet, grouped into lists by destination and delivery date, then walked through material ready, validation, shipping and close. The availability guard is the part that stops the classic failure: before a box can be allocated to today's list, the system reserves the full ordered quantity of every live list with an earlier delivery date.

  • Spreadsheet import that finds the header row itself, so column order does not matter
  • Refuses the scan when on-hand stock minus this pick would fall below what earlier deliveries need
  • Reserves an earlier list's entire requirement, not just the part it has yet to prepare
  • Rows that fail validation are logged with part and PO number, and the rest of the import still goes through
  • Shipping labels issued at validation, with poka-yoke label matching available for sites that need it
Feature 02 - Storage

Put-away that chooses the bin for you

Pallets are built by scanning boxes, capacity-checked against the pallet quantity in the catalogue, and put away into a shelf slot or a floor bin. When no location is given, the automatic bin search picks one in a defined priority order that keeps parts grouped without over-filling a single bin.

  • Prefers a bin already holding one to three pallets of the same part
  • Falls back to a completely empty bin rather than mixing parts
  • Uses an over-full bin holding the right part only as a last resort
  • Shelves are modelled as rows and columns, with blocked positions and a live occupancy map
  • Pallet capacity comes from the catalogue, so an over-built pallet is refused at the scan
Feature 03 - Control

Quarantine, counting and 22 reports

Quality can block a pallet or move it into quarantine, and blocked stock stops counting as available immediately. Inventory runs as a session: a snapshot, scan-to-count, then four result lists separating what matched, what deviated, what was never found and what was found but not expected.

  • Blocking and a four-state quarantine flow: held, rejected, to release, released
  • Counting sessions with a snapshot, so the count is measured against a fixed baseline
  • Deviations split into four result lists rather than one undifferentiated variance figure
  • Twenty-two reports covering stock, pallets, quarantine, deliveries, activity and receipts
  • Every report exports to a spreadsheet for audit or analysis
FAQ

Questions a warehouse manager asks first

The answers that come up in every deployment.

Before allocating a box to a picking list, the system totals the full ordered quantity of that part on every live list with an earlier delivery date, and refuses the scan if the remaining on-hand stock would drop below that figure. It reserves an earlier list's whole requirement, not just the portion still unprepared, because a half-prepared delivery still needs all of its material. Blocked, quarantined and already-staged stock is excluded from the on-hand side of that calculation.

Because they are two different figures and both are correct. Gross quantity is everything physically on a pallet. Available quantity is gross minus what has already been allocated to a delivery. On top of that, blocked, quarantined and truck-shadow stock is physically present but deliberately not available. The reports name which figure they are showing.

There are three different ways a pallet stops existing, and they are not interchangeable. Emptied box by box during picking, it ends as deleted. Validated as a whole onto a shipping pallet, it ends as composed. Issued to a production floor, it ends as done. All three are gone from stock, but only the first is a deletion, so a report that seems to be missing pallets is usually looking for the wrong one of the three.

The automatic bin search runs in priority order: first an active bin already holding between one and three pallets of the same part, then a completely empty active bin, and only as a last resort any bin already holding that part. The order deliberately prefers keeping a part together over filling an empty slot.

As a spreadsheet. The system locates the header row by looking for the Material and PO Number columns within the first twenty rows and then maps every column by its heading, so column order does not matter. Rows are grouped into picking lists by destination and delivery date. A row that names an unknown or deactivated part is rejected and written to the import log with its part and PO number, while the valid rows are still created.

Five roles: Administrator, Warehouse, Quality, Logistics and Material Planner. Quality alone handles blocking and quarantine decisions, Material Planner owns orders and the supplier catalogue, and only administrators see user management. Two protections cannot be overridden: you cannot delete your own account, and you cannot delete the last remaining administrator. Note that the reports area is not role-restricted by default, which is a deliberate carry-over that can be configured per deployment.

As a session rather than a freeze. Opening a session takes a snapshot of expected stock, operators then scan to count, and closing produces four separate result lists: what matched, what deviated in quantity, what was expected but never found, and what was found but not expected. Splitting them out matters, because the four have different causes and different fixes.
Ecosystem

What it connects to

QC-WMS holds the stock. These handle what happens on either side of it.

Transport

QCLOT

Once a delivery is staged and loaded, QCLOT prices and books the freight that carries it, and handles the compliance paperwork.

Learn More
Production

Jidoka Kanban

Supply to floor is where the warehouse ends and the line begins. Jidoka Kanban governs how that material reaches and feeds the line.

Learn More
Quality

TML

When material is scrapped rather than shipped, TML captures the loss at the work cell and puts a cost on it.

Learn More
Get Started

Start with the count you cannot currently trust

Most deployments begin with one part family or one shelf block, prove the count holds, then extend to the whole warehouse.

Warehouse diagnostic
We walk your flow and name where the count breaks
See a live demo
The scan flows, on your own part numbers
Pilot one area
One shelf block or part family, live in weeks
Request a demooffice@share-it-smart.com Β· +40 736 909 455