Eleven questions this week, and a good number of them share an uncomfortable question underneath the obvious one: how do you actually know? Not what a courier reports about its own delivery record. Not what a single survey response implies about service quality generally. Not what a packing station says used to happen; what a scan can prove happened, correctly, whether anyone was watching or not. The theme this week isn't features. It's verification: not "can the system do X", but "can it prove X actually happened, to someone who wasn't in the room." 

Can a Mis-Pick Be Caught before It Ships? 

Yes: Helm's digital picking won't validate a scan if the wrong item's been picked, so staff scan the location barcode and then the product barcode, and a mis-pick gets caught right there at the pick, not weeks later when a customer complains. 

That's the whole shift in where the error gets caught: at the shelf, by a scanner that doesn't care whether anyone's paying attention, instead of in an inbox, from a customer who now has to prove they got the wrong thing. 

Can You Check Real Carrier Delivery Performance? 

Yes: Helm's customer care and tracking section shows genuine on-time delivery percentages, filterable by date range and by carrier or service level, independent of what the courier itself reports. 

It often reveals a lower rate than the carrier's own headline figures, which tells you something about whose number you've been building service promises around. A courier grading its own homework was always going to mark generously. The point of tracking it independently isn't to catch anyone out; it's to know which service level is actually holding up before a customer tells you first. 

Does Helm Support B2B & Pallet Carriers, Not Just Parcels? 

Yes: alongside standard parcel carriers such as Royal Mail, DHL, DPD, FedEx, UPS and Evri, Helm supports pallet carriers including TPN, UPN, Pallet Track and Pallet Ways, plus reseller aggregators such as AGL. 

A parcel-only integration list is a reasonable proxy for how seriously a platform takes B2B, since pallet freight is a genuinely different shipping problem, not just a bigger box. A vendor whose B2B story is "we can send a pallet too, eventually" is usually describing something bolted on after the fact, not built for it. 

Can Purchase Orders Be Raised Automatically from Demand Data? 

Yes: Helm looks at transaction data, including minimum order quantities, supplier relationships, inventory and open-order demand trends, and lets you raise a purchase order in a couple of clicks from that analysis. 

The manual version of this is a spreadsheet somebody updates when they remember to, built from a gut feeling about what sold well last month. The automated version is the same decision, made from the same data that's already sitting in the system, just made before the stock actually runs out rather than after. 

What's the Difference between Assembly Kits & Group Products? 

Helm's Assembly app, part of the Ultimate plan, tracks builds from component stock for products that genuinely need assembling. Group products instead let you sell a single SKU made up of several existing inventory items without any formal build step. 

The distinction is whether a build actually happens. A kit that's physically assembled from parts needs tracking through that process; a bundle that's just three existing products sold together under one listing doesn't need a build record, it needs the stock counted correctly against all three at once. Treating both the same way is how a bundle ends up with a phantom build log for something nobody actually built. 

Can Stock Counts Run While Picking Is Still Happening? 

Yes: Helm moves a digitally picked item into a virtual picked location the moment it's scanned, so what a counter finds in the physical location during an ABC stock count reflects genuinely available stock, letting counts run alongside live picking and packing. 

ABC counting itself just means counting higher-value stock more often and lower-value stock less, which Helm supports by letting you set count frequency per product and bulk-generate count tasks for everything due in a date range. The bit that actually matters operationally is the virtual-location trick: without it, a count and a pick happening in the same aisle at the same time would disagree with each other, and someone would have to decide which one was wrong. With it, there's nothing to disagree about. 

Can You Apply a Peak-Season Carrier Surcharge Temporarily? 

Yes: Helm lets you update a courier service's price for a surcharge period, such as over Christmas, and change it back afterwards, with customer pricing recalculating automatically each time. 

A general percentage-based price-increase tool covers an across-the-board rate rise if every service needs adjusting at once, rather than one at a time. The part worth noting is "changed back afterwards": a surcharge that never gets switched off stops being a surcharge and starts being a price rise nobody agreed to. 

Can 3PL Clients Get Their Own Branded Portal & Shipping Rules? 

Yes: Helm's Fulfillment app gives a 3PL a control panel showing all clients, open orders, SLA breaches and stock alerts, alongside a fully branded portal, light or dark mode, the client's own logo and colors, where their own customers can view stock, orders and tracking. 

Inside that portal, clients can set their own shipping rules before an order reaches fulfillment, choosing from whichever couriers the 3PL has made available to them, with orders released either manually or automatically. That's the difference between a 3PL that's a black box you post stock into and one where the client can actually see and shape what happens to their own orders. The branding is nice. The control over which courier gets used and when is what actually changes how a client's operation runs. 

Can a Customer Satisfaction Score Reflect Genuine Service, Not Just One Bad Mood? 

Yes: Helm blends the customer satisfaction survey rating with actual SLA performance, so one low rating doesn't tank the overall score if the underlying SLA record is genuinely strong. 

A survey on its own measures how someone felt in the 30 seconds after clicking a link, a real data point, but not the same thing as service quality; blending it with the SLA record is what turns a mood into a metric. The survey can also be switched off entirely for a specific client if it's not the right measure for that relationship, which is its own quiet admission that a single number was never going to tell the whole story. 

How Does Billing Flow into Xero for a Fulfillment or Reseller Operation? 

Helm's preferred and supported accounting integration is Xero: charges are calculated on your chosen billing cycle, weekly, bi-weekly or monthly, and pushed through automatically. 

A draft invoice appears in Xero on the billing date, ready to review, with a payment link already attached for the client. The part worth noticing is "draft": nothing goes out to a client unreviewed, which is the right amount of automation for a step where a wrong number on an invoice is a client-relationship problem, not just a data-entry one. 

Can Orders Be Batch-Dispatched without a Picking Step? 

Yes: on a basic, non-stock-managed Helm setup, no picking step is required at all; you filter or select orders sitting in new order status and go straight to batch dispatch. 

Batches of roughly 400 to 500 orders or more have been handled this way successfully, which says something about how far you can run on a stripped-down setup before you actually need the full picking machinery. It's the same principle as going live on a single default stock location: start with the minimum the order volume actually requires, and add the structure back in only once the volume demands it, not before. 

Eleven questions, and underneath every one of them the same test: not whether Helm can do the thing, but whether it can prove the thing happened, correctly, to someone who wasn't standing there when it did. A returns process nobody quarantines is a returns process running on trust. A mis-pick nobody catches until the customer does is a system taking your word for it. Trust is fine until it's expensive. Proof is cheaper, and it was sitting in the data the whole time. 

If any of this is the gap you've been quietly working around on your own account, bring it to a demo instead of a workaround: talk to us.