Lodsted Help

For managers and admins

What the Admin level unlocks, the daily and weekly checks worth doing, and the alerts that need a person rather than a retry.

What Admin adds

  • Stock adjustments and Bulk Adjust; Sync Inventory (push counts to the store now).
  • The Import buttons on Locations and Inventory (spreadsheet imports).
  • Wave definitions and the Recalculate allocations button.
  • Kits, and switching on Shopify stock tracking from the product review.
  • Deleting purchase orders and removing PO lines. (Backing out a receipt is Owner only.)
  • On Shipments: Retry Fulfillments, Resolve Carriers, Re-push, changing a shipment's status, and opening a processed shipment. Undoing an auto-move.
  • Team and every Settings tab.

Keep the Admin list short; everything a packer or picker needs works at the User level.

Daily

  1. Dashboard. Backordered above zero: look at the Inventory page's Backordered column and the open POs. On Hold: who owns each one. Active Waves older than yesterday: complete or reset them.
  2. Shipments › Needs attention. Every row there is a package that left but whose store push did not succeed, or a shipment that could not be processed. Read the note, fix the cause, Re-push or Dismiss. Do not leave Abandoned rows: the customer has no tracking.
  3. Replenishment. Glance at the report; generate moves when pick bins are running low or a big wave is coming. It is run as needed, not on a schedule.
  4. Waves. Run the definition buttons left to right, top of the list first: stock is reserved as each wave is created, so a later button cannot take units an earlier one already claimed. Check the eligible counts; create. Confirm auto-moves are completed as they are done.
  5. End of day. USPS manifest printed and handed over; shipments processed (click Process Shipments after the last label if you do not want to wait for the sync).

Weekly

  • Transactions filtered to type Adjusted: every adjustment has a reason; patterns point to a bin, a SKU or a process.
  • Transactions filtered to Shortfall: bins that were short at ship time need a count.
  • Replenishment › Undersized: bins too small for their velocity.
  • Inventory › Unavail above zero: stock parked in inactive locations; decide whether to move it or reactivate.
  • Setup page: anything still open (product tracking review after new products, printing setup for a new bench).

Alerts and what they mean

EmailCategoryAction
Order changedShippingAn order In Wave or Printed was edited in Shopify; Lodsted did not apply it. The email lists the wave, bin and changes. Decide with the packer: ship as is (address or method changes), or remove the order from the wave and re-wave it (line changes). One email per order per four hours.
Fulfillment push failed / not verifiedShippingOpen the order in Shopify. If it is fulfilled there, Dismiss the shipment; if not, fix the cause (often the order was edited or canceled at the store) and Re-push.
Carrier mapping failedShippingAn imported shipment used a service name Lodsted does not know. Add the mapping, then Resolve Carriers on the Shipments page.
Inventory shortfallInventoryCount the listed bins; adjust with a reason. Check whether an auto-move was skipped.
Allocation driftAdminLodsted rebuilt reservation counts after a wave and they differed from what it was tracking. Usually harmless after manual interventions; recurring drift means someone is resetting waves or adjusting allocated stock mid-pick.
Shopify Shipping purchase timed outShippingCheck the order in Shopify for a label before buying again.
Plan and usage (cheaper plan, 80% of cap, cap reached, new waves paused)Admin, and the ownerExtra orders are adding up. If the email names a plan that would cost less, change plan on the Setup page. After the cap, the email gives the time new waves pause (one business day later); a plan change lifts it as soon as Shopify confirms. See Billing.

Wave definitions worth having

Most warehouses settle on: a Rush definition at the top (priority flag or overnight method), one per shipping speed, a singles definition for single-line orders (fast to pick and pack), and a catch-all last. Test each with the editor's Test button; set each definition's cart size to the cart that type is picked into (up to 250), since a wave never resizes itself, and give bulky items their own smaller-cart definition above the general ones. Details and examples: Waves.

Team

Staff appear after first opening Lodsted from Shopify. Set level and email on the Team page; deactivate leavers rather than deleting, so their name stays on the audit trail. Email is used only for display and alerts.

Settings that bite when wrong

  • Warehouse time zone: wrong zone, wrong PO dates and a "today" that rolls over mid-shift.
  • Ship-from address: wrong origin, wrong rates and labels.
  • Alert email addresses: still the installer's inbox months later.
  • Shipping method mappings: an unmapped checkout option means every such order defaults to Standard at the bench.
  • Holidays: missing closures understate the handling time Lodsted reports.

Recovering from mistakes

MistakeRecovery
Wave created with the wrong definitionReset it before printing; orders return to Downloaded.
Wave printed, then found wrongReset it; the printed tag is removed in Shopify. Collect the paper.
Shipment processed for the wrong orderStock is already deducted and the store told. Adjust stock with a reason; fulfill the correct order; correct the wrong one in Shopify.
Replenishment move generated but not doneUndo it on the Waves page; stock returns to bulk in the system.
Counts look wrong after an interventionWaves › Recalculate allocations, then compare Available with the shelf.
Product tracking switched on with zero on handThe storefront shows sold out. Receive stock or adjust it in; the next push fixes Shopify.