How is Clasto different from QuickBooks or an ERP like SAP?
QuickBooks is built around the ledger; SAP is built to be configured into any industry. Clasto is built around the container. The shipment is the primary record, and purchase orders, supplier invoices, documents, duty, freight, and payments all attach to it. Accounting is native, so nothing has to be re-keyed — but you are never configuring a generic module to behave like a shipment.
Do I need to be technical to run it?
No. If your team can run a spreadsheet and a WhatsApp group, they can run Clasto. Onboarding loads your suppliers, ports, and open containers for you, and the day-to-day flow is a list of containers with what each one still needs.
Does it work in Spanish?
Yes — English and Spanish are both first-class. Each user picks their language, and the data is shared. Your ops lead can work in Spanish while your accountant works in English, on the same records. Documents render in the language of whoever receives them.
What does the AI actually do — and can it change my numbers?
It reads documents. Commercial invoices, packing lists, and bills of lading come in as PDFs or photos, and Clasto extracts the line items, quantities, and amounts into a draft. It cannot post anything. A person reviews the draft against the source document and approves it before it becomes a record. Every approval is logged with who and when.
How long does onboarding take?
Most importers are running live containers within two weeks. The first week loads suppliers, products, ports, and any containers already in transit; the second runs your live shipments alongside your old process until you're ready to drop it.
What counts as a container for pricing?
One shipment record created in the month, regardless of size — a 20′, a 40′, or a consolidated LCL booking each count as one. Containers already in transit when you start are not counted. Above your bracket, each additional container is $10.