Integrations

All integrations, in one place.

Every marketplace you sell on, every carrier you ship with, every retailer you EDI into. 60 direct connections plus 100+ retailer compliance maps, native, partner-built, or custom.

Showing 60 of 60 · hover any logo for details

Don't see your stack? Tell us what you run — custom EDI and API mappings shipped in 4 to 8 weeks.

API capabilities

Build your own connector.

If your stack isn't in the grid, our REST API ships every order, inventory change, and shipment event as a JSON webhook. Replay any failed event, pull historical data on demand, scope tokens per environment so dev never touches prod.

Documented in OpenAPI 3.1, versioned, sandbox that mirrors production. Most teams ship their first integration in under a week.

Request API docs Talk to engineering

Webhook · shipment.created

POST /webhooks/shipment.created
Authorization: Bearer vtx_live_••••

{
  "event":        "shipment.created",
  "occurred_at":  "2026-05-15T14:23:11Z",
  "order_id":     "ord_4kQ9pYz",
  "tracking": {
    "carrier":         "ups",
    "service":         "ground",
    "tracking_number": "1Z999AA10123456784",
    "label_url":       "https://api.vertex.com/..."
  },
  "node":         "atl-01",
  "cutoff_met":   true
}

EDI capabilities

Ship into the big-box stack.

We run SPS Commerce as our EDI broker and write custom maps per trading partner. Every 850, 856, 940, and 810 transaction is monitored against the retailer's routing guide before the trailer leaves our dock.

B2B retail orders

Pallet-out, retailer-spec carton labels, ASN sent at dock seal, BOL signed off in the same workflow as DTC.
B2C dropship

Orders placed on the retailer's site flow into our WMS and ship direct to the customer. Tracking writes back to the retailer for their notifications.

100+ retailer connections mapped across the US and Canada. Custom maps for new trading partners ship in 4 to 8 weeks.

Scope an EDI integration

Onboarding split

What you set up. What we do.

Most of the integration work is on us. Your side is small, and we tell you exactly what we need before kickoff.

Your side

Brand onboarding tasks

Roughly half a day of focused work across a dev lead and an ops lead. We send a one-page checklist.

Shopify or marketplace API key

Generate a custom app token with read_orders, write_fulfillments, read_inventory scopes. We never need write_orders.
SKU catalog (CSV or shared sheet)

SKU, title, dimensions, weight, HS code (if you ship international), and any bundle / kit mappings.
Label and packaging spec

Branded packing slip template, dunnage rules, insert preferences, and any retailer-specific carton labels.
Carrier accounts (if you have negotiated rates)

We load your UPS / FedEx / DHL account numbers. If you don't have negotiated rates, you ride ours.
ERP credentials (if applicable)

Read access to the item master and write access to sales-order / item-fulfillment records.
Decision: who owns the customer support inbox?

You, us, or split. We default to escalating WISMO and damage tickets to your team within 1 hour.

Our side

Vertex responsibilities

Everything below is included in your standard agreement. We don't bill setup hours for native integrations.

Webhook handlers and retries

Exponential backoff with dead-letter queue. Every failed webhook is replayed and surfaced in the exception queue within 5 minutes.
Multi-carrier rate-shop configuration

Per-zone, per-weight rules across your accounts plus EasyPost regionals. We re-tune quarterly against your shipping mix.
Inventory reconciliation

Nightly cycle-count writeback to your storefront and ERP. We catch drift before it becomes oversell.
Returns + RMA processing

Inbound receive, condition grading, restock-or-grade-out decision, and refund trigger written back to Loop / Returnly.
SLA monitoring + the exception queue

Late shipments, missing tracking, address failures, customs holds. Our ops team works the queue 24/7.
API version upgrades

When Shopify GraphQL Admin changes versions or Amazon SP-API deprecates an endpoint, we ship the upgrade. You don't see it.

Talk to engineering

Talk to a Vertex integration engineer.

Bring your stack diagram. We'll tell you which connectors are native, which need middleware, and what the timeline looks like. No procurement gate, no sales scripts. Twenty minutes with the team that builds it.

Contact Sales