FAQ
Questions that come up.
Slipmill takes order JSON and returns a branded US Letter PDF. The answers below stay on this page, not the homepage.
A packing slip PDF API accepts the order JSON you already have and returns a print-ready packing-slip PDF. Slipmill’s route is POST /v1/render with the x-sm-key header. One POST is one render. The response is application/pdf, US Letter, synchronous.
JSON. Slipmill is not HTML-to-PDF and not a bring-your-own-template renderer. There are two locked templates we own: packing-slip and invoice. You send data. We print it.
A packing slip is fulfillment: order id, ship-to, from, SKU, qty, optional notes and tracking. An invoice is billing: line amounts in cents, optional tax_cents and due date. We print tax if you send it. We do not calculate tax. The invoice is not a customs commercial invoice.
We print the customer packing slip and the billing invoice. We do not print a freight or customs packing list, HS codes, or a commercial invoice for the border.
Send a brand name, an optional hex accent, and on paid plans one https logo URL. The layout stays ours. Starter PDFs print a small Slipmill footer. Pro and Scale hide it.
No. Slipmill is not a tax engine and not a customs product. tax_cents is printed as sent. We do not pick a jurisdiction, file anything, or emit a commercial invoice.
No. Those products sell postage, labels, and carrier forms. Slipmill prints a packing slip or invoice from OMS JSON. We do not buy postage or talk to a carrier.
Starter is $0, no card, 50 renders per month, with a small footer. Pro is $49 for 3,000 renders and no footer. Scale is $149 for 15,000 renders, then $6 per 1,000 overage. Public names are Starter, Pro, and Scale.
Yes. Use an HTTP Request node, Webhooks by Zapier, or a Make HTTP module. Send header x-sm-key. Slipmill is not a listed n8n, Zapier, or Make app. Guides: /n8n-packing-slip, /zapier-packing-slip, /make-packing-slip.