DIY Developer Guide: Building Custom Integrations for WeSupply

Overview

WeSupply is a post-purchase experience platform that offers shipment tracking, order notifications, returns management, and in-store pickup solutions for eCommerce businesses. This DIY Developer Guide for WeSupply provides a structured framework for building secure, scalable, and efficient custom integrations with eCommerce platforms, ERP systems, and customer experience solutions.


Prerequisites for WeSupply Integrations

  • WeSupply API access credentials (API Key)
  • Familiarity with:
    • RESTful APIs
    • OAuth 2.0 or API Key Authentication
    • JSON data formatting
  • Tools: Postman, WeSupply API Documentation, SDKs (Python, Node.js)

Step 1: Authentication for WeSupply Integrations

WeSupply APIs use API Key authentication.

Authentication Example:

Authorization: ApiKey YOUR_API_KEY

All API traffic must be sent over HTTPS.


Step 2: Endpoint Discovery and Data Mapping

Common API Resources:

  • Orders
  • Shipments
  • Returns
  • Notifications
  • Store Locations

Process:

  • Review WeSupply API documentation thoroughly.
  • Map your ERP or eCommerce platform fields (e.g., order ID, customer email) to WeSupply fields.

Important considerations:

  • Proper mapping of order and tracking information
  • Ensuring return reasons and statuses are standardized
  • Store location data structure for in-store pickup solutions

Step 3: Building Integration Workflows

Integration Patterns:

  • Inbound (to WeSupply): Push new orders, shipment updates, and returns data.
  • Outbound (from WeSupply): Retrieve customer notifications, return statuses, and store pickup availability.

Example: Creating an Order

POST /api/orders
{
  "orderNumber": "ORDER12345",
  "customerEmail": "customer@example.com",
  "items": [
    { "sku": "SKU001", "quantity": 2 }
  ]
}

Example: Retrieving Return Status

GET /api/returns/RETURN_ID
Authorization: ApiKey YOUR_API_KEY

Step 4: Error Handling and Pagination

Error Handling:

  • Capture HTTP status codes and WeSupply-specific error messages.
  • Implement retries for rate limits (429) and server errors (5xx).

Pagination:

  • Use page and pageSize parameters for large result sets.

Example:

GET /api/orders?page=2&pageSize=50

Step 5: Testing and Validation

  • Validate order creation, shipment updates, and return management workflows.
  • Use Postman or sandbox environments for full API testing.
  • Conduct load testing for high-volume order and return syncs.

Step 6: Deployment and Security

  • Deploy integrations on secure cloud platforms (AWS, Azure, GCP).
  • Store API Keys securely using secret managers.
  • Enforce HTTPS/TLS for all data transmission.
  • Implement real-time error monitoring and detailed logging.

Step 7: Maintenance and Monitoring

  • Monitor WeSupply API status updates and releases.
  • Set real-time alerts for failed transactions.
  • Track KPIs such as notification delivery rates, return processing times, and store pickup success rates.

Optional Enhancements

  • Middleware integration (MuleSoft, Celigo, Boomi) for cross-platform automation.
  • Real-time dashboards for post-purchase journey monitoring.
  • Webhook implementations for instant shipment and return status updates.

Summary

Building custom WeSupply integrations enables businesses to deliver outstanding post-purchase experiences, enhance customer satisfaction, and streamline returns and pickups. This DIY Developer Guide for WeSupply provides a complete blueprint for building secure, scalable, and efficient integrations.


Apiworx is dedicated to helping eCommerce businesses scale faster than ever possible before by streamlining and managing complex OmniChannel data flows, we save our customers time and money, allowing them to scale their businesses faster and more effectively.  We focus on automation and integration of often-overlooked back-office systems and processes such as order and inventory management.   We work with major partners in the industry and build best-in-breed automation and integration solutions.