How to connect to Porterchain

Upload a CSV (or spreadsheet export) with your orders. We agree on the columns once with you—recipient, address, time window, reference—and you reuse the same format for each run. No API or integration build required. Ideal for recurring routes where you already maintain a list; ops can run this daily or weekly. We validate the file and schedule from it.

Submit orders programmatically via our API. Create shipments, get status and ETA, and sync with your WMS, OMS, or e-commerce stack. We provide documentation and support for authentication and payloads. Built for teams that are ready to automate. We'll confirm schema and capabilities for your use case before you build.

We support EDI-based order and status flows for merchants who already use EDI with partners. Our adapter architecture lets us align on transaction sets and connectivity; we map and test with you. Suited for B2B and retail replenishment where EDI is the standard. We're clear about what we support so you can plan your pipeline.

Not ready to automate? Our ops team can enter orders on your behalf—from email, PDF, phone, or a shared spreadsheet. You send the run list; we load it and schedule. Low friction for small teams or pilots. We'll outline a path to CSV or API when you're ready to scale.

Send orders or manifests to a dedicated inbox. We parse and schedule from your email — same format each time so the process is repeatable. Works well for daily or weekly runs without touching an API or portal. Simple for dispatchers and ops.

Optional SMS prompts for ETA updates and exception alerts tied to the live capacity run — so receivers and ops stay aligned without a disconnected text thread.

Where enabled, WhatsApp can deliver tracking prompts and exception coordination for field receivers — always linked back to the shipment record and proof closeout.

Push status, exception, and proof events to your WMS or OMS. Schemas and signing live in developer docs; commercial capacity still starts with a written quote.