FedEx
Tracking events, service context, and exception or customs-hold codes.
INTEGRATIONS
Connect the systems around every exception.
Veztra brings tracking scans, order context, support conversations, and operational notifications into one shipment record. Approved tickets and emails move through the connection they belong to; replies and status changes return to the case, while alerts and supported events reach the systems your team watches.
Connection model
Context in. Controlled action out.
SIGNALS IN
Tracking scans · orders · replies
CONTEXT BUILT
Shipment · buyer · deadline · evidence
WORK PREPARED
Ticket · email · document · decision
ACTION CONTROLLED
Reviewed by an operator before it matters
No connector silently changes a carrier address or submits a claim, customs document, refund, or replacement on your team's behalf.
INTEGRATION DIRECTORY
01 · CARRIER TRACKING
See the parcel signal before choosing the response.
Carrier connections bring tracking movement and exception context into the shipment record. Veztra uses that evidence to detect consequential cases, apply carrier-aware timing, and prepare the next step for review.
SUPPORTED CONNECTIONS
UPS
Tracking events, address-correction signals, and delivery-schedule context.
USPS
Tracking history, delivery events, and parcel exception signals.
DHL Express
International tracking and customs-clearance status signals.
Canada Post
Domestic and cross-border events, including failed-attempt and notice scans.
CSV fallback
Mapped shipment and tracking imports when a direct carrier connection is not in use.
CONNECTION CONTRACT
- What comes in
- Status and scan history, timestamps, service information, and provider-specific exception or clearance codes. Available fields vary by carrier.
- What Veztra does
- Veztra turns those signals into prioritized exceptions, failed-delivery cases, delivery-verification checks, and a prepared recommendation, not a second tracking feed.
- Human-control boundary
- These are tracking connections. Veztra does not buy labels, reroute parcels, directly change a carrier address, or submit a carrier claim through them.
02 · COMMERCE
Put order and customer context beside the tracking number.
Commerce connections explain what a parcel represents: the buyer, order value, fulfillment, and line items behind it. That context helps the queue distinguish an ordinary delay from work that deserves immediate attention.
SUPPORTED CONNECTIONS
Shopify
Orders, customers, fulfillments, tracking references, and order-value context.
WooCommerce
Orders, customers, line items, and available HS-code or origin product metadata.
BigCommerce
Orders, shipping and tracking, line items, and available customs product fields.
CONNECTION CONTRACT
- What comes in
- Order and buyer details, fulfillment and tracking references, item and value context, plus customs metadata when the connected store provides it.
- What Veztra does
- Veztra links the parcel to its commercial context and uses the record to prepare outreach, claim evidence, and editable commercial-invoice fields.
- Human-control boundary
- Commerce sync does not silently issue refunds, create replacements, change fulfillment status, or publish a buyer correction. Operators confirm consequential changes in the appropriate system.
03 · HELPDESK & COMMUNICATIONS
Keep approved communication in the tools your team already watches.
Veztra prepares carrier and buyer communication with the shipment record attached. Connected helpdesks can receive approved work and return conversation state, while email and Slack cover outbound delivery and operational awareness.
SUPPORTED CONNECTIONS
Zendesk
Approved tickets, follow-up replies, and ticket status or response context.
Gorgias
Approved carrier tickets and replies, tagged with shipment context.
Freshdesk
Approved tickets and replies with resolved or closed status returned to Veztra.
Intercom
Approved conversations and replies with closed or reopened state returned.
Generic outbound email
A configured fallback for approved carrier follow-ups without a helpdesk connection.
Resend
Delivery from a verified sender for approved carrier email and Morning Brief digests.
Slack
Morning Brief delivery and rate-limited critical operational alerts.
CONNECTION CONTRACT
- What comes in
- Conversation identifiers, replies, and status from connected helpdesks, along with the sender or channel configuration used for outbound delivery.
- What Veztra does
- Approved tickets and replies can be delivered through the connected helpdesk or email path. Responses return to the activity record; Slack carries briefs and alerts.
- Human-control boundary
- Carrier and buyer messages stay operator-approved. Scheduled briefs and configured Slack alerts are notifications. They do not execute a recovery action or alter a shipment.
04 · WEBHOOKS & API
Connect an internal system through a defined contract.
For workflows outside the native connectors, Veztra provides scoped building blocks rather than a promise that arbitrary data or actions will work automatically. Your team decides which supported exchange belongs in the operating model.
SUPPORTED CONNECTIONS
Inbound shipment webhook
A workspace-specific endpoint for mapped shipment updates when configured in production.
Outbound operational webhook
Selected shipment and workflow events delivered to your endpoint, with signing when configured.
Workspace API keys
Revocable credentials for supported, workspace-scoped programmatic access.
CONNECTION CONTRACT
- What comes in
- Mapped shipment updates can enter through the inbound endpoint. Selected operational events can leave through an outbound endpoint; API keys authenticate supported direct requests.
- What Veztra does
- Use these surfaces to connect a warehouse, reporting layer, or internal operations service where the published request and event contracts fit the job.
- Human-control boundary
- The inbound webhook is not a universal schema or action bus. External callers cannot bypass Veztra's approval gates for messages, documents, or case decisions. A claim marked filed in Veztra records internal workflow state. It does not mean Veztra submitted the claim to a carrier.
YOUR STACK, WITH CLEAR BOUNDARIES
Bring the systems your team already runs.
We'll map which connections supply context, which can deliver approved work, and where the operator remains the final control. If a direct carrier connection is not the right starting point, CSV keeps the first workflow practical.