For CartonCloud

Everything LogisticsUI does on top of CartonCloud

CartonCloud runs your warehouse. LogisticsUI does the admin around it. It reads the documents. It builds the orders. It fixes what broke overnight. It works through the CartonCloud API, so nothing changes inside CartonCloud itself and none of your existing CartonCloud integrations are touched.

Watch it work

Works on any CartonCloud plan with API access.

The LogisticsUI chat creating six CartonCloud orders from an uploaded PDF, with each tool call listed as it completes.
Customer names, products and totals are examples, not real client data.
39 orders. One prompt.

39 orders got rejected overnight. Missing SKUs. Some had 40 lines. That's a whole morning of typing. It took about 10 minutes.

A week. Now a day.

Planning stock across 100 SKUs took two people a full week. They pulled numbers out of four systems by hand. Now it's one question.

Friday. 7:00 AM.

Every Friday it checks the week's new Shopify SKUs against CartonCloud and emails the list. Nobody used to build that report.

What it does

The jobs it does in CartonCloud

Not a demo list. This is what CartonCloud 3PLs have it doing every day.

packing_slips.pdf → 7 orders

Builds orders from documents

Packing slips, emailed POs, spreadsheets. It reads them, checks stock, and creates the sales orders and POs. Your customer keeps sending what they already send.

If a product code on the document is not in CartonCloud yet, it says which ones and offers to create them, then carries on in the same run. Order entry →

24 SKUs created · 39 orders resynced

Fixes what the integration rejected

A product is in Shopify but not in CartonCloud, so the order bounces. It finds them, adds them, and pushes the orders through.

You can do it once when you notice, or set it as a standing check that runs before anyone gets in. Most 3PLs start with the first and move to the second. Alerts & workflows →

"how many shipped in March?"

Answers stock and dispatch questions

How many went out between two dates. What's on hand. What's awaiting stock. Ask it like you'd ask a person. One sentence back. Reporting →

runs Fri 07:00 · emails the gaps

Runs your standing checks

The check you keep meaning to do on Monday. Tell it once and it runs on its own. You only hear from it when a person is needed.

One customer set hers up the morning after the feature shipped, without being asked. Friday at 7am, new Shopify SKUs checked against CartonCloud, gaps emailed. Alerts & workflows →

Doc 60 · BC liquor

Produces the compliance paperwork

Doc 60 for BC liquor shipments, built from the order and the pricing on the sheet. Not typed out again by hand. Doc 60 →

in build with one client

Month-end billing

Storage and handling run against your own rate card, from what actually moved. We're building this with one 3PL now.

Orders being built from attached PDFs, with LogisticsUI resolving SKUs that do not match the ones in CartonCloud.
Real screen from a client account. Customer names, SKUs and document contents are masked; nothing has been added or rearranged.
Your rules

Tell it once. It remembers.

Every warehouse has rules that live in one person's head. Tell LogisticsUI the way you'd tell a new hire. It does that from then on, on every order.

You don't write it down anywhere. You don't build anything. You just say it in the chat.

It matters most on the customers nobody else covers for. When the person who knows a client's quirks is off, the rules are still there and the orders still go in right.

  • "No expiry date on this customer's products."Taught once. It never asks again.
  • "This client counts in cases, not units."Applied to every order from them since.
  • "Orders for this brand ship from Kelowna."Routed to the right warehouse without being asked.
  • "Always use the PO number as the reference."Set on the order every time, so it matches at invoicing.
Alongside CartonCloud

It reaches the rest of your stack

CartonCloud is the middle of the stack, not all of it. A question doesn't stop at the WMS, so neither does it. It reads the store, the shipping tool and the invoicing tool, and writes back where it needs to.

ShopifyShipStationGoogle SheetsHiveageJobberEmail

…and almost any other system with an API or webhooks.

From a real customer
I have it open permanently now. I'm in LogisticsUI as often as I'm in our WMS.

Senderoo, 3PL warehouse

FAQ

Questions we get asked

Does it replace CartonCloud?

No. CartonCloud stays in charge. It's still your WMS and your source of truth. LogisticsUI reads from it and writes into it through the API. The same actions your team does by hand today.

Do I need CartonCloud's official integrations?

No. That's most of the point. The customers who cost you the most time are the ones who were never going to integrate. The ones sending a PDF or a spreadsheet. It handles those.

What CartonCloud plan do I need?

Any plan with API access. If you're not sure what you're on, send us a screenshot of your plan page and we'll tell you.

Does CartonCloud know about this?

We use their public API the way any connected tool does. We're not a CartonCloud product and we don't speak for them.

Is my data stored?

We keep a working copy of what your systems tell us so questions come back fast, plus the files you upload. Your data is not used to train any model.

What does it cost?

It starts at $249 a month and moves up with how much you run. There's a one-time setup fee to hook up your systems. See pricing →

Get started

See it run on your own CartonCloud

Bring your worst packing slip. Or a pile of rejected orders. We'll run it live on your own account. Thirty minutes, no slides.

Or watch it work on our YouTube channel.