Data comes in, goes out, and connects
Patisco covers quote-to-shipment. Your ERP, accounting and warehouse connect in four ways.
No code, standard codes, code, and for AI
No code: Excel and PDF.
Products, customers, suppliers and documents import and export; documents render as PDF with your letterhead and terms.
Document values map to international standard codes.
Currency (ISO 4217), Incoterms, quantity and package units (UN/ECE Rec. 20/21), ports (UN/LOCODE) and HS codes — in the picker your own wording sits above the standard code, and what gets stored maps to the standard. When a buyer’s system needs structured data, the source values are already right. Actual EDI message output (EDIFACT/X12/UBL) is built to the spec your buyer provides.
Code: API.
GraphQL and REST, scoped to your account’s permissions: products, parties, quotes, orders, shipments, shared files. Read Patisco documents from your system, or push ERP masters in.
For AI: MCP Server.
Let your company’s own AI tools read and write Patisco data under the same permissions and confirm-before-write rule.
Same rules as the AI assistant
Your account’s permissions, every write logged, data never trained on or shared.
How to start
During onboarding we map the touchpoints together: what comes from ERP, what goes back, how often. You don’t figure it out alone.
Book 20 minutes, bring your ERP vendor →20-minute online meeting · pick a slot on the calendar