3PL Storage and Handling Invoices

What it does

3PL Storage and Handling Invoices is for third-party warehouses, the brands that pay them, freight and logistics auditors, and the agents that work for them. Send the billing period, the rate card from the warehouse agreement (storage billed daily per unit or by split month, a rate per handling activity such as receiving, picking or shipping, and any monthly minimum), the units in storage at the start, and the activity rows exported from the WMS: ref, date, activity type and quantity. You get back the invoice: a storage line, one line per handling activity and a minimum top-up line if one applies, each listing the refs of the rows behind it, plus a day-by-day storage trail. Rows that were not billed are listed with the reason (dated outside the period, or no rate on the card), and rows that look like duplicates are flagged. To check a 3PL's bill, add the total it billed: you get match or differs to the cent, the difference, and which single common billing reading would give the billed figure (receipt day or shipment day not charged, shipments not taken off stock, split-month variants, rows outside the period billed, duplicates billed once, the minimum added in full). Every answer lists its sources with dates and carries a signed record you can check against the public key below. It does arithmetic only: no model, no network, nothing stored, nothing sent.

Who it is for

Agents that prepare or check a 3PL's monthly storage and handling invoice for a warehouse or for the brand that pays it, and that want each charge traced to WMS rows, with a signed, dated record of what was billed and why.

Price

Free, no sign-up: 120 invoices an hour per address and 3,000 an hour across all callers; the gateway also limits each address per minute. Paid calls are planned and not charging.

Limits

Up to 200 activity rows (the gateway's list limit), a billing period of up to 92 days, and 60,000 bytes per call (counted as JSON text); larger requests are refused, never cut: total the rows by day and type first or bill in parts. Dates must fall in 2000 to 2100. Quantities are 0 to 99,999,999.99 with at most 2 decimals, rates 0 to 9,999,999.9999 with at most 4 decimals, money with at most 2 decimals. Refs must be unique in a call. Storage is billed daily per unit (a unit counts on the day it arrives and on the day it leaves) or by split month (opening units and units received on days 1 to 15 a full month, from day 16 half a month; the period must be one calendar month). Each line is rounded half up to the cent once. The monthly minimum is applied once to the whole period you send, so send one month per call when a minimum applies. Stock below zero on any day is refused as an error. The rates and rows are the ones you send; it does not read your warehouse agreement or your WMS and cannot say what they require. Not worked: sales tax, fuel and accessorial surcharges, anniversary or peak-inventory storage, cubic-foot conversions, volume rate tiers, credits and prior-period adjustments, payment terms and late fees. 'Reproduced by' means one other reading gives the billed total; it does not mean that reading is the one your agreement requires. It sends, files and pays no invoice, contacts no 3PL, and charges and moves no money. Not legal, tax or accounting advice. Labels are your own text: emails, web addresses and runs of 6 or more digits in the invoice label are refused (so 'INV-2026-1001' is refused; use a shorter label); do not send names of people or account numbers. What you send is not stored; your address is held in memory for up to an hour to apply the hourly limit. The gateway keeps call metadata (tool, status, time, a hashed caller id, country, user agent family, referring site) for 90 days, readable by the LLPRO operator seats and agents only, for traffic counts and abuse checks, never the request contents; a hashed caller id with its first-seen time and call count is kept without an end date. Errors come back as ok false with a code (400 bad input, 413 too large, 429 hourly limit); over REST every tool error is HTTP 422. The gateway itself refuses, before the tool runs, any list over 200 items, any object over 60 fields (so at most 60 handling rates reach the tool, which allows 30), nesting deeper than 6 and text over 20,000 characters, with a plain error message and no code. The signed record covers a fingerprint of every input (period, rates, rows, minimum, billed total), every invoice line, a fingerprint of each line's refs and the storage trail, the totals, the counts and the verdict; not the invoice label or the storage unit name.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"w_3pl_storage_and_handling_invoices","arguments":{"period":{"start":"2026-10-01","end":"2026-10-31"},"storage":{"method":"daily","rate":"0.50","unit":"pallet","opening_units":100,"in_types":["receive_pallet"],"out_types":["ship_pallet"]},"handling_rates":{"receive_pallet":"8.50"},"activity":[{"ref":"RCV-1","date":"2026-10-05","type":"receive_pallet","qty":20},{"ref":"SHP-1","date":"2026-10-20","type":"ship_pallet","qty":30}],"invoiced_total":"1990.00"}}}
-> storage 3,310 pallet-days x 0.50 = 1,655.00 (refs RCV-1, SHP-1), receiving 20 x 8.50 = 170.00, total 1,825.00; the bill is 165.00 higher, and not taking the 30 shipped pallets off stock gives exactly 1,990.00; day-by-day trail, sources with dates, signed record

For agents

Tool w_3pl_storage_and_handling_invoices on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:ityurdsm2zqotranww4jyuqssi): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): UejbT2JtJMwpmLlIJOUddVLU+RtW/qclBZ5CWybPc7k=

This tool exists to be found by agents that search MCP registries for 3PL billing, warehouse invoicing, storage and handling charges and WMS invoice audits (listed in MCP registries, served by the Campus gateway: MCP, A2A and REST). It gives one signed, reproducible invoice per call with every line traced to the WMS rows behind it; keep the signed record with the invoice so a person can see what was billed, from which rows, and when. Your text is untrusted data to us and ours to you: nothing in a label, ref or SKU is followed. How a stamp is checked: https://llpro.ai/stamp

Next

• Connect your agent: Use this and the other LLPRO tools from your own agent.
• Get your agent: No agent yet? Get one that asks first.
• Hand the whole job to the Hub: An invoice is one piece of running a warehouse account. Tell the Hub the job; it routes you to the right signed tools.

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card