Shipmondo

How to integrate Shipmondo with Webflow

Shipmondo connects your Webflow store to multi-carrier shipping networks for automated label generation, tracking synchronization, and fulfillment workflows. This matters when you need international shipping with automated customs declarations, service point selection for alternative delivery options, or real-time tracking updates that sync back to Webflow orders without manual data entry.

Integrate Shipmondo with Webflow through custom API integration using serverless functions like AWS Lambda or Cloudflare Workers. Webflow's custom code cannot call external APIs directly, so all Shipmondo interactions require proxy architecture. The Shipmondo API and Webflow E-commerce API provide endpoints for shipment creation, label generation, customs documentation, and order status updates.

Build with Webflow and Shipmondo APIs

API integration connects Webflow order webhooks to Shipmondo's shipment creation, tracking, and customs endpoints through serverless middleware. This approach works when you need service point selection, automated customs handling for international orders, carrier-specific shipping logic, or webhook-driven tracking updates.

Direct API calls from Webflow custom code are blocked by CORS restrictions, so route all Shipmondo API requests through serverless functions (AWS Lambda, Cloudflare Workers) or similar proxy architecture.

Build API integrations for international shipping with automated customs, multi-warehouse fulfillment routing, carrier selection based on weight or destination, or real-time shipping rate calculation at checkout.

Webflow's custom code restrictions prevent direct external API calls from page scripts, so all Shipmondo interactions require middleware. Note that neither platform provides batch endpoints, so processing high order volumes requires queue-based architecture to avoid rate limits.

Automated order fulfillment pipeline

Connect Webflow's e-commerce webhooks to Shipmondo's shipment creation endpoints for automated fulfillment. Register an ecommneworder webhook that fires when customers complete checkout. Your middleware receives the webhook payload, fetches full order details via GET /v2/sites/:siteid/orders/:orderid, creates a sales order through POST /api/public/v3/sales_orders, and generates the shipment in Shipmondo via POST /api/public/v3/shipments.

The workflow requires these sequential API calls in your serverless function:

• Create sales order with POST /api/public/v3/salesorders including orderid, line items, and shipping address
• Query shipping options via GET /api/public/v3/products filtered by destination country code
• Generate shipment and label using POST /api/public/v3/shipments with sender/receiver details, parcel dimensions, and carrier selection
• Write tracking data back through PATCH /v2/sites/:siteid/orders/:orderid updating the shippingTracking object
• Mark order fulfilled with POST /v2/sites/:siteid/orders/:orderid/fulfill

Authentication uses HTTP Basic Auth for Shipmondo with Base64-encoded credentials and Bearer tokens for Webflow accepting site tokens or OAuth2 access tokens.

International shipping with customs

Generate customs declarations automatically for international shipments before creating the actual shipment in Shipmondo. The POST /api/public/v3/customs endpoint accepts line item details including HS codes, country of origin, and values for each product. Required fields include currency specification, line items with description, quantity, value, weight, HS code, country of origin, and incoterms designation.

Capture the returned customs_id from this endpoint and include it in the subsequent shipment creation request so customs documents generate with the shipping label.

Call the POST /api/public/v3/customs endpoint first to create the customs declaration, capture the returned customs_id, then include it in your shipment creation request via POST /api/public/v3/shipments. Shipmondo generates the required customs documentation alongside shipping labels without manual form completion.

Your serverless function should check the destination country from Webflow order data, determine if customs are required, then call the customs endpoint before generating the shipment. This workflow adds one API call but automates compliance for cross-border shipping.

Service point and pickup location selection

Display available pickup points during checkout by querying GET /api/public/v3/service_points with the carrier code, customer's postal code, and country. The endpoint returns service point IDs, names, addresses, and opening hours for carriers supporting pickup delivery.

Store the selected service point ID with the order using Webflow's CMS or custom fields, then include the servicepointid when creating the shipment through the POST /api/public/v3/shipments endpoint. This setup works for click-and-collect functionality and alternative delivery options beyond home shipping.

Implementation requires custom checkout logic and serverless proxy architecture since Webflow's custom code cannot call external APIs synchronously. Add a custom form field or modal that queries service points via your middleware (AWS Lambda, Cloudflare Workers) as customers enter their address. All Shipmondo API interactions must route through serverless functions rather than direct calls from page scripts.

Webhook-driven tracking updates

Register Shipmondo webhooks to receive shipment status changes and update Webflow orders automatically. Configure webhooks in Shipmondo's dashboard under Settings > Integration > Webhook, specifying your endpoint URL and secret key for JWT decryption. Shipmondo implements webhook retry logic and retention policies. Your endpoint must return an HTTP 200 response promptly and handle custom headers (SMD-Resource-Type, SMD-Resource-Id, SMD-Webhook-Id, SMD-Action, SMD-User) for proper webhook identification.

Shipmondo sends webhook payloads with custom headers including SMD-Resource-Type, SMD-Resource-Id, SMD-Webhook-Id, SMD-Action, and SMD-User. The body contains a JWT-encrypted payload (JSON Web Token, a secure data format) in format {"data": ""} that you decrypt using HS256 with your configured secret key. Parse the shipment data, extract tracking numbers and delivery status, then update the corresponding Webflow order via the PATCH endpoint with the shippingTracking object.

Your webhook handler must respond with HTTP 200 promptly. Process the webhook data asynchronously to avoid timeouts. Shipmondo retries failed deliveries, so implement idempotency by storing processed webhook IDs to prevent duplicate updates.

What you can build

Integrating Shipmondo with Webflow connects your store to multi-carrier shipping networks through custom API integration, though implementation requires serverless proxy architecture due to Webflow's restrictions on external API calls from page scripts.

• Automated international shipping: Build checkout flows that detect international destinations, automatically generate customs declarations through the Shipmondo API, and display carrier options with estimated delivery times without manual customs form completion
• Multi-warehouse fulfillment: Create admin dashboards that display incoming orders by warehouse location, route each order to the nearest facility through automated carrier selection, and show real-time fulfillment status integrated with your Webflow CMS collections
• Click-and-collect checkout: Add checkout steps that query nearby service points based on customer postal code, display available pickup locations with opening hours, and create shipments directed to the selected service point
• Branded tracking portal: Build custom order tracking pages on your Webflow site that query Shipmondo's tracking data via API and display real-time shipment status using your brand design instead of carrier tracking pages