Tell it what you need. Cargo finds the best supplier.
The AI sourcing agent for B2B buying — it compares catalogs, sends RFQs when prices aren't public, and turns the winning quote into a purchase order, bill, and journal entry.
How the sourcing agent works
Cargo does the legwork; you make the decisions.
- 1~1 minRequestDescribe the item, quantity, and deadline in plain language — part numbers help but aren't required.
- 224–72hReview quotesCargo sends RFQs to 3–6 matched suppliers and lines every reply up in one comparison.
- 3Records auto-createdOrderThe winning quote becomes the purchase order, bill, and journal entry.
What you can source
Packaging first — pick a category and send the RFQ as-is. For corrugated boxes we also publish a free comparison of 22 Japanese makers. Not on the list? Ask us first.
Runs on Sanka ERP
Cargo isn't a separate tool with an export button. The winning quote becomes a purchase order in Sanka ERP — and everything that follows stays in the same workspace, under the same approvals.
- Purchase orders & billsThe winning quote becomes a PO; receiving turns it into a bill — no re-keying.
- Journal entries & accountingEvery purchase posts a journal entry — the books follow automatically.
- InventoryReceived goods update stock levels in the same workspace.
- Per-supplier price tablesNegotiated prices are records — Cargo checks them before asking for quotes.
Mayu KawasakiSanka Inc.Purchase Orders
Take the Towa Metal quote through to purchase order.
- Approval routed & granted
- Created PO-0189
- Drafting the bill & journal entry
Spend data in. Cost-cut proposals out.
Add your expenses, bills, and usage data, and AI organizes them into one monthly view — then comes back with grounded proposals like "these boxes cost more than market; a re-quote can bring them down." Each proposal hands straight off to the sourcing agent above.
Spend monitor — from data to proposals
- Add your spend. API keys for Anthropic and OpenAI, Sanka AI usage built in — and CSV or manual entry for everything else: purchasing, utilities, subscriptions, outsourcing.
- AI organizes it. Every record is normalized into one monthly view — totals, per-source breakdown, six-month trend, month-over-month deltas.
- Get cost-cut proposals. AI flags what can come down — versus market prices and your own history — and each proposal is one click from a re-quote.
Free spend diagnostic
See this month's savings potential — free, no commitment.
Start a free Sanka workspace, connect your AI sources by API key or upload a spend CSV, and get the one monthly view of where your money goes. The diagnostic is free and yours to keep — and when a proposal is worth taking, the sourcing agent above turns it into an RFQ.
What Cargo does
The machinery behind the form — all of it live today.
Frequently asked questions
Can I use Cargo today?
Yes. Send a free RFQ from the form above — we dispatch it to suppliers within one business day. The spend monitor is also available today inside Sanka workspaces.
Is it free?
Submitting RFQs and comparing quotes is free. Nothing is charged before you place an order.
How many suppliers receive my RFQ?
The Cargo sourcing desk normally selects three to six suppliers that fit your requirements. You can also point Cargo at your existing suppliers.
What if no quote arrives?
We will explicitly tell you — no silent dead ends — and offer a one-click way to retry with adjusted requirements.
Do I need to be using Sanka ERP?
No. RFQs are free and don't require Sanka ERP. A free Sanka workspace is created with your request, and the purchase orders and bills it produces live there as records.
What does the spend monitor do?
Upload your expenses or connect your spend sources, and AI organizes them into one monthly view and recommends where to save — including the best-fit suppliers to re-quote.
Does the spend monitor pull expenses and bills from Sanka ERP automatically?
Not yet — that sync is in development now. Today, AI sources connect by API and every other spend comes in by CSV or manual entry.
Where is my data stored?
In your Sanka workspace, governed by the same permissions and logs as everything else. API keys are stored like other integration credentials and never exposed to the browser.
Does it work in Japanese?
Yes — RFQ (相見積) exchanges, documents, and support all work in Japanese.