Every warehouse runs on two rulebooks. One is written down: the SOP in the binder, the settings someone picked at go-live. The other is what actually happens at four o’clock on a Friday, when a picker has a scanner in one hand, three units in the other, and a trailer waiting.

Take scanning. Ask anyone how to cut picking errors and they’ll say scan every unit. It sounds rigorous, and it looks great on an audit. In practice it produces more errors, not fewer. Once a control asks for more effort than the job needs, people find a way around it. After that it isn’t really a control anymore. It’s theater.

That was the thread running through this week’s calls: the rule that sounds sensible and the rule that works kept turning out to be different rules. Put-away stock shouldn’t just go to the first empty location. Damaged stock shouldn’t be marked “not restockable.” An order weighing exactly 5kg isn’t “less than 5kg.” Each one arrived as a dull little settings question, and each one was really a policy decision. A policy you didn’t choose is still a policy. It’s just one nobody signed off.

Why Does Helm Let You Scan Once?

Helm doesn't force a scan of every unit: you scan a product once to confirm it, the system shows the full expected quantity automatically, and you can accept that quantity or edit it down. This applies when receiving, picking, or packing stock.

It's deliberate, and the reason is more interesting than it sounds. Forcing repeated scans tends to produce more errors in practice: staff scan three times, say, but physically pick only two. A control that asks for more effort than the task needs gets worked around, and once it's being worked around it stops telling you anything. One scan and a quantity you confirm puts the check back where a person is actually paying attention.

What Should You Do with Stock That Arrives Damaged?

Helm's recommended approach is to receive damaged stock in fully first, including stock that arrives already damaged from a supplier, and then process it out separately by stock adjustment with a recorded job reason.

From there the stock can be destroyed, returned to supplier, donated, or moved into a dedicated damaged tote, and quarantine or checking locations can be set up for anything that needs a closer look. The tidier-looking shortcut is marking it "not restockable," which removes it from the system with no audit trail behind it. Tidying and deleting the evidence are the same action here. The record is what you'd reach for if anyone later asks where the stock went.

Why Doesn't Put-Away Stock Go to the First Empty Location?

Helm sends put-away stock to whichever location is set as the highest priority for that product's movement, not automatically to the first empty location, and the destination can be edited when the movement is created.

First empty is how a system behaves when it has no opinion about your warehouse. Priority is how it behaves once you've given it one. Stock can also go straight from the delivery location into a pick face: you specify the destination when creating the movement, and nothing requires it to pass through bulk storage first. Read more on putaway.

Should Uninspected Stock Be Available for Sale?

That's your call in Helm, because a location's status for channel availability is set independently of whether it's pickable. A goods-in or quarantine location can be marked as active for sellable stock while staying excluded from picking.

Whether stock can be sold and whether it can be picked are two different questions, and a listing shouldn't go dark just because the answer to one of them is "not yet." This keeps a listing showing stock as available even before formal receipt is completed.

What Happens to an Order That Weighs Exactly 5kg?

In Helm, an order weighing exactly 5kg falls into the next weight band up from a "less than 5kg" rule.

Every band has an edge, and the package sitting on that edge goes somewhere. That gives you precise control over how orders are routed between bands, so it's worth knowing which side the line falls on before you write them.

Can Helm Handle Amazon Vendor Central as Well as Seller Central?

Yes: Helm supports Amazon Vendor Central, where Amazon buys and resells the stock itself, alongside its standard Amazon Seller integration for D2C orders.

The two are different arrangements: with Seller Central you sell to the shopper, and with Vendor Central Amazon is your customer. For businesses that sell both FBM and FBA (fulfilled by merchant and fulfilled by Amazon), Helm can also bring FBA order data in as reference only, automatically marked dispatched.

Why Are Stock Counts Wrong When Two Systems Share a Sales Channel?

Helm should be the only system syncing stock to a given sales channel location, because a second platform updating the same store or location can conflict with it, and that is the likely cause of quantity discrepancies.

A stock count goes wrong fastest when two systems are both confident they own it. Running Helm for two different countries or operations wouldn't recreate the problem, because each Helm instance connects to its own distinct sales channel location and syncs stock only there.

None of these would make a slide, which is rather why they matter. The obvious rule and the right rule aren't always the same one, and it's better to find that out on a quiet afternoon than mid-shift.

If you'd like us to walk through any of these against your own setup, bring your awkward cases to a call: talk to us.