Nine questions this week, and not one of them arrived with a dramatic story attached, no warehouse director at the end of their patience, no supplier crisis. What they share instead is cost: every one is a small setting that's cheap to get right and expensive to get wrong. The expensive part doesn't show up in the moment. It shows up later, as a stock feed that's gone to zero for no reason anyone can trace, or a customer dispute with no evidence on either side. Ask the question before you need the answer, not after you've already paid for skipping it. 

Can You Track a Batch Back to Every Order If There's a Recall? 

Yes: Helm tracks batch and expiration dates, with FEFO built in, and traces serial numbers, batch numbers and expiration dates against every order as it's scanned out, giving full traceability back to a shipment. Full batch-dispatch reporting isn't a native feature yet, but you can build it yourself, to your own specifications, using the "Build Apps with AI" tool in the dashboard, which takes around ten minutes. Most vendors will say "coming soon" and leave you waiting on their own backlog. Helm closes that gap by giving you the tools to build exactly what you need instead. 

Can You Prove the Right Order Was Packed If a Customer Disputes It? 

Yes: Helm's Dispatch Terminal records scan proof, and optionally video, of every order as it's packed at a centralized packing station, giving you an audit trail if a discrepancy gets raised later rather than a shrug and a "we're pretty sure we got it right." Video capture is optional, not mandatory, which is the right call. Not every warehouse needs video evidence of a jiffy bag. It's easy to see why the ones shipping high-value or dispute-prone items would want it regardless. 

Do Automated Shipping Rules Cost Extra? 

No: Helm includes automated shipping rules as standard, not as an upsell like some competing platforms charge for. Its filters can combine criteria such as next-day orders, priority services and destination country, and get saved as rules that pick the right courier and service automatically. Skip it, and the alternative isn't a person doing the same job more carefully. It's a person doing it under time pressure, getting it right most of the time, and nobody finding out about the exceptions until a customer complains. 

What's the Difference between Syncing Stock & Downloading Products? 

Helm's "Download products" setting pulls SKU, image, dimension and weight data from a sales channel and should be switched on. Its "Auto sync stock" setting instead pushes stock levels back to the channel, and should stay off until the stock data in the hub is accurate, since switching it on too early zeroes out live stock on the channel. Naming the two settings clearly, instead of leaving them vague, isn't a small choice. It's the difference between a mistake you can undo and one that's already live on the storefront by the time you notice. 

Do You Need Full Warehouse Locations Set Up Before You Can Go Live? 

No: Helm lets you go live on a generic default stock location, with full location and aisle breakdowns built out later once you've set up your own warehouse properly. There's a genuine "basic warehouse mode" in Helm for this: batch label printing and API-driven order intake, with full location, picking and stock-movement tracking switched on later when it's needed. You don't need to know your warehouse before you can start shipping from it. You need to start shipping to find out what your warehouse actually needs to look like. 

Can You Build Your Own Reports without a Developer? 

Yes: Helm's in-dashboard, no-code app builder, built on an MCP integration with Claude AI, lets non-technical users build their own custom read and write dashboards and reports without a developer. It's the same underlying problem as the recall question above: you can never pre-build every report a growing operation will eventually need, so what actually matters is how fast you can build the one you didn't know you'd need yet. The usual version of this feature elsewhere involves submitting a ticket, waiting for a developer's sprint to have room in it, and getting back roughly what you asked for, eventually. Helm skips the queue entirely. Every IT team has a backlog. This is the one request that never has to join it, and the report can exist the same afternoon someone decides they need it, not the sprint after next. 

Does the System Support Webhooks for Custom Integrations? 

Yes: Helm's webhook settings page lets you configure the event type (order created, order updated, order dispatched, or stock updated), along with method, target URL, authentication and headers. Full API documentation exists alongside it, and webhooks are the preferred method over polling. Polling isn't hard to build; it's the lazy option, which is exactly why so many platforms default to it and still call it "real-time." Polling means your system asking "has anything changed yet?" every few minutes, forever, and getting "no" most of the time. Webhooks mean being told the second something changes. The difference isn't academic when the thing that changed was a stock level: the gap between the change and you finding out about it is exactly the window in which a customer can buy something you don't actually have. 

How Long Does a New Courier Integration Take? 

Helm's Carrier Gateway is self-service: pick a courier from the list, add your own credentials, and it's connected in about two minutes, no waiting on a developer's calendar. That's the default now, worth knowing before you assume every new courier means logging a ticket and joining a queue. If you'd rather Helm's team built it for you instead, that's typically two to four weeks, depending on how quickly the courier's own API documentation and test credentials become available. 

How Long Does Onboarding Actually Take? 

Most Helm customers are fully live within two to three weeks, or around 30 days if the data needs more work. The fastest on record was three days, stock take included, which tells you the bottleneck is rarely the software. Three days is the exception, not the promise, and any vendor who quotes it as the rule is setting you up for an uncomfortable conversation later. Helm's migration itself is a one-to-one, hand-held process: store connection, test orders, test picks and packs, stock-sync checks, then a phased go-live that starts with the smallest store first, so nobody's biggest revenue line is the guinea pig. 

Nine questions, and the pattern underneath all of them is the same one: nothing here goes wrong loudly. It goes wrong quietly, later, as a discrepancy nobody can trace back to the toggle that caused it. That's precisely why it's worth knowing the answer before you need it, not after the stock count comes back wrong. 

If any of this is the exact configuration question you've been meaning to ask on your own account, bring it to a demo rather than guessing: talk to us.