Inbound & Receiving
Scan-driven receiving, putaway, and LPN tracking with client-specific rules and full inventory transactions.
LumiLogix is one warehouse system that runs the whole floor — dock bookings, receiving, picking, counts, value-add and the invoice at the end of it. Built for 3PLs who are tired of holding it together with spreadsheets.
30 minutes, on the live product. No slide deck, no sales team.
One system replacing the spreadsheet stack
From the moment a truck books an appointment to the day the invoice goes out, inventory, labour and billing stay in step — because it's all one system rather than four that need reconciling.
Scan-driven receiving, putaway, and LPN tracking with client-specific rules and full inventory transactions.
Order-linked dock appointments, gate entry, and a live timeline so no trailer waits without a reason.
Allocation, picking, packing slips, staging, and shipping — with cross-dock flows for fast turns.
Cycle count schedules, adjustments, and item history give you a defensible, audit-ready stock position.
Kitting, unkitting, and bagging jobs with bills of material and operator productivity tracking.
Billable events, storage accrual, recurring charges, auto-invoicing, aging, and multi-currency (CAD / USD).
Shift templates and self-service schedules, a time clock, task assignment, and operator productivity feeding payables.
Client and carrier portals with per-category document visibility, order requests, scheduled reports, and an in-app support desk.
Ask questions about your own data and turn emailed orders into drafts. Permission-scoped, off by default, and a human commits every write.
We're honest about being early — no client is live on LumiLogix yet, so you won't find invented testimonials here. What you will find is a system that has been built properly and that we'll show you working, end to end, on the first call.
Separation between clients isn't a filter in a screen that someone can forget — the database itself refuses to return another client's rows.
If the Wi-Fi drops mid-aisle, the scan is already saved on the device. It re-sends itself when signal returns — and never double-counts.
The whole operator experience runs in English, French and Spanish, with written training guides in all three.
Thousands of automated tests run on every single change, and we exercise the product daily against a full demo warehouse.
Not a feature list — the real workflows your team runs every shift. Screens shown are illustrations of the product, drawn from our demo dataset.
Handheld scanner workflows walk operators through each line. Client-specific receiving rules catch exceptions before they hit the floor, and every unit lands in a location and an LPN.
Appointments are linked to real orders, drivers check themselves in from a gate QR code, and a live timeline shows every door in use. Dock billing settings turn detention and demurrage into revenue, not arguments.
Orders flow from allocation to a packed, staged, and shipped state with printed pick and packing slips at each step. Fast-moving freight skips storage entirely with cross-dock staging.
Cycle count schedules keep accuracy continuous instead of waiting for a year-end shutdown. Counters work blind or from a worklist, stock found where it shouldn't be gets created on the spot, and every adjustment is reasoned and logged.
Build kits from a bill of materials, break them back down with unkitting, and run bagging jobs — all while tracking operator productivity so you can bill the labor accurately.
Storage, handling, and value-add generate billable events as work happens. Storage accrues daily against a snapshot ledger rather than being guessed at month-end, monthly minimums settle at close, and posted invoices are immutable — corrections are credits, not edits.
Build the week from shift templates and let operators confirm or reject their own shifts by email. Work is assigned as tasks, time on task is recorded, and the same record that proves the work got done is the one that pays for it.
Ask plain questions about your own warehouse instead of hunting through screens, and let emailed purchase orders arrive as reviewable drafts. The assistant is off until you turn it on, every tool it calls is re-checked against your permissions, and it never commits a record — a person does, from the normal screen.
Work flows through one system, so the receipt your operator scanned is the line your client gets billed for. Nobody re-types it into a second tool.
Carriers book their own dock slots and drivers check themselves in from a QR code at the gate. Your team receives against the order on a handheld — and if the aisle has no signal, the scan is saved on the device and sent when it comes back.
Putaway to a location and a licence plate. Every move is recorded, so counts happen continuously on a schedule instead of shutting the building down once a year.
Allocate, pick, pack, stage and ship — or cross-dock straight through for same-day turns. Pick lists and packing slips print at each step.
Handling and value-add become billable lines as the work finishes, and storage accrues daily rather than being guessed at month-end. Invoices go out on a schedule, in CAD or USD, straight into QuickBooks.
Most vendors make you find this out in month three. LumiLogix is a new product — the warehouse system is complete enough to run your floor end to end, and we'd rather show you the two things that aren't finished up front than have you discover them later.
Receiving and putaway, licence-plate tracking, locations, outbound allocation, picking, packing, staging, shipping, cross-dock and stock transfers.
Order-linked appointments, carrier self-booking, door blocks, operating-day rules, driver self check-in, gate entry and no-show handling.
Cycle count schedules, blind or worklist counting on the scanner, found-stock creation, reasoned adjustments, and lot / serial / expiry tracking.
Kitting and unkitting from bills of material, plus bagging, repack, wrapping and strapping jobs, with operator productivity captured per job.
Billable events, daily storage accrual, month-close minimums, recurring charges, rate cards, tax codes, auto-invoicing, aging and payments.
Shift templates, self-service schedules, time clock, task assignment, operator teams, and payables built from the work actually recorded.
Client and carrier portals with per-category document visibility and scheduled reports, plus in-app support tickets that reach our desk by email.
A proper connector rather than a file drop: invoices queue and retry, customers and A/R accounts map to yours, and payments recorded in QuickBooks come back into LumiLogix. CAD or USD.
Ask questions about your own warehouse in plain language, and let emailed purchase orders arrive as drafts your team reviews. Runs on Claude or GPT — your choice, your API key. Off unless you turn it on, spend-capped, and a person commits every write.
Built as a mapping engine, so we can take your partner's actual file and map it during onboarding rather than telling you to change it. Carrier load tender (204) works end to end today. The warehouse documents — 940, 945, 943, 944, 846 — are registered and partly mapped, but each one still needs wiring per partner, and there's no SFTP or AS2 transport yet. Tell us your partners and we'll tell you plainly what's configuration and what's build.
Want to know exactly how something behaves before you commit? Ask, and we'll show you in the product rather than on a slide.
As a 3PL you carry your clients' stock and their data. Everything below is on from day one — not a premium tier, not a hardening project for later.
In most systems, keeping clients apart depends on every screen remembering to filter correctly — and one missed filter is a data breach. We push that rule down into the database itself, so it holds even if something above it is wrong. Your client logs in and the storage layer will not hand over anyone else's rows.
Every scan is written to the handheld before it's sent anywhere, and only cleared once the server confirms it. Drop the device, close the app, walk out of coverage — the work comes back and re-sends itself. And it can't double-count: if the server already recorded that pallet, the retry is recognised rather than received twice.
Modern password hashing, a strong password policy, and login errors that don't tell an attacker whether an account exists.
Authenticator-app codes with backup recovery codes and admin reset — and you can require it for every admin, with a grace period while they enrol.
When an employee leaves, deactivating them ends their session immediately. No waiting for a token to expire on its own.
Repeated password guessing is slowed and then locked out automatically, per account and per address, and the attempt is recorded.
Adjustments, voids, rate changes and logins are all written to an audit log you can read in the app — useful for your clients as much as for you.
Systems that talk to LumiLogix get their own scoped keys you can revoke, restricted to the addresses you allow. Nobody's account is shared.
Once posted, an invoice is fixed. Corrections are credits — so the document your client is holding still matches the one in your system.
Automated security and dependency scanning runs on every change we make, alongside the test suite. Nothing ships around it.
What comes in the box, versus what you'd normally buy piece by piece. Where ours is partial, the cell says partial.
| Capability | Spreadsheets & email | WMS + add-ons | LumiLogix |
|---|---|---|---|
| Dock scheduling tied to real orders | × | Often an add-on | ✓ Built in |
| Counting that runs continuously | × | Varies | ✓ Scheduled |
| 3PL billing & invoicing without re-keying | × | Separate module | ✓ Built in |
| Storage accrued daily, minimums at month-close | Manual | Varies | ✓ Built in |
| Shifts, time clock & operator pay | Separate tool | Separate tool | ✓ Built in |
| Client & carrier self-service portals | × | Usually extra | ✓ Included |
| Scanning that survives a dead spot | × | Rare | ✓ Built in |
| Client separation enforced in the database | × | Usually app-level only | ✓ Built in |
| Two-factor & a full audit log | × | Varies | ✓ Built in |
| QuickBooks with retry & payments back | × | Usually export only | ✓ Connector |
| Operator screens in English, French & Spanish | × | Varies | ✓ All three |
| Multi-currency (CAD / USD) | Manual | Varies | ✓ Native |
| EDI for your trading partners | × | Usually costly | Mapped per partner |
Your accounting, your scanners, your partners' documents. Where something is partial, we say so.
Invoices queue up and retry if something's wrong, your customers and A/R accounts map to theirs, and payments recorded in QuickBooks flow back into LumiLogix. CAD or USD.
We take your partner's actual file and map it during onboarding, rather than handing you a fixed list of documents to conform to.
Packing slips, invoices and documents email themselves — templated per client — with order threads and attachments filed against the order.
Works with standard handheld barcode scanners and label printers. The screens are built for scanner input, not adapted to it.
Import and export CSV and XLSX across items, clients and inventory — including saved import profiles per client, so month two isn't as painful as month one.
Scoped, revocable API keys for anything you want to connect — never a person's login.
Seventeen built-in reports covering revenue, dock, receiving, inventory and activity — all exportable, and five of them can email themselves to a client on a schedule.
Optional, and not tied to one vendor: choose Anthropic's Claude or OpenAI's GPT from a dropdown in Settings. Bring your own key for whichever you pick, switch later without touching anything else, or leave the feature switched off entirely.
We haven't set list prices yet, and we'd rather say that than invent one. Our first warehouses get priced accordingly — here's how the packages are shaped, and the number comes out of a conversation about your volume and dock count.
Let's talk
One warehouse, getting off spreadsheets.
Let's talk
Multi-client 3PLs that bill for what they do.
Custom
Several sites, with systems to connect.
No sales team to get past — you'll be talking to the people who wrote the code.
Not yet — you'd be among the first, and we'd rather you hear that from us than find out later. The product is built and we run it daily against a full demo warehouse, but there's no live client site, so we have no customer references or throughput figures to quote. What we can do is show you the whole thing working on a call and let you judge it yourself.
Pricing that reflects the risk you're taking, direct access to the people writing the code rather than a support queue, and real influence over what gets built next. The trade is that you're first — you'll find things we haven't, and we'll fix them fast.
We haven't onboarded a live warehouse yet, so we won't pretend to a number. What we can tell you is the work involved: importing your items, locations and clients (bulk CSV and XLSX import is built in), configuring receiving and billing rules to match how you actually operate, and training operators on the scanner screens. Written training guides for the operator, client and carrier workflows already exist in English, French and Spanish.
LumiLogix TMS is the next product we're building, and it'll be a standalone system rather than a bolt-on. It isn't available today. If transportation matters to your decision, say so on the call — we'll be straight with you about timing, and early input genuinely shapes what gets built.
Nothing is lost. The scan is saved on the handheld before it's sent anywhere, and it's only cleared once the server confirms it. It survives a reload, a crash and a flat battery, and re-sends itself when signal comes back. It also can't double-count — if the server already recorded that receipt, the retry is recognised rather than processed again.
No. LumiLogix runs in a browser and works with standard handheld barcode scanners and label printers. The scanner screens are designed for hardware-scanner input from the start.
The work itself creates the charges. Receiving, handling, storage and value-add each raise a billable line as the task completes, priced by your client contracts and rate cards. Storage accrues daily rather than being estimated at month-end, monthly minimums settle at close, and invoicing runs on a schedule with aging and payment tracking, in CAD or USD. You can still add manual lines when you need to.
Yes, and it's included rather than an upsell. Clients get self-service visibility into their inventory and orders and can request orders; carriers can book and manage their own dock appointments. Access is invite-based and scoped, and you control which document categories each client sees.
Yes — English, French and Spanish are all built in across the whole operator experience, and we check automatically that the three stay in step as we add features. The written training guides exist in all three languages too.
QuickBooks: yes, and it's a real connector rather than a file you export and import by hand. Invoices queue and can be retried individually if something's wrong, your customers and A/R accounts map to theirs, mappings are checked against your actual company file before anything posts, and payments recorded in QuickBooks come back into LumiLogix. CAD or USD.
EDI: partial, deliberately. It's built as a mapping engine, so we can take a real file from your partner and map it during onboarding instead of asking them to change. Carrier load tender (204) works end to end today; the warehouse documents are registered and partly mapped but each still needs wiring per partner, and there's no SFTP or AS2 transport yet. Tell us your partners and we'll tell you what's configuration and what's build.
Only if you switch it on, and only for the clients who agree to it. The assistant does two things: answers questions about your own warehouse in plain language, and turns emailed purchase orders into drafts your team reviews. It's off by default, and a person always commits the record through the normal screen — it never writes anything itself.
You're not locked to one AI vendor. An admin picks the model in Settings — Anthropic's Claude or OpenAI's GPT — and you bring your own API key for whichever you choose. Switching later is a dropdown, not a project.
On the data question, which matters more for a 3PL than for most: any individual client can refuse AI processing, and that's honoured without turning the feature off for your other clients. Their documents are parsed the old-fashioned way and their rows are filtered out before the assistant ever sees them. On top of that, sensitive fields are stripped before anything reaches a model, the assistant can only see what the person asking could already see, every call is logged including refused ones, and you set a hard spend cap plus per-user daily budgets.
Yes. You build the week from shift templates, operators confirm or reject their own shifts by email, and a time clock plus task assignment records who did what and for how long. That same record drives operator payables — so the work that proves itself is the work that gets paid, with no separate spreadsheet to reconcile.
Access runs on granular roles and permissions, with optional two-factor that you can require for admins. Crucially, keeping clients apart isn't left to each screen remembering to filter — it's enforced down in the database, so it holds even if something above it is wrong. Sessions can be ended instantly, password guessing is locked out automatically, and every security-relevant action lands in an audit log you can read. There's more in the Security section.
Book 30 minutes. We'll walk your operation through the live product — not a slide deck — show you exactly how billing and the dock would work for you, and tell you straight about anything it doesn't do yet.