Commerce Data

​

🧭 Overview

The Commerce Data APIs allow you to populate Loop’s ecosystem with commerce data from any source—your commerce platform, ERP, OMS, middleware, or custom systems. These APIs are intended for custom integrations where Loop doesn’t have a prebuilt app for your commerce platform; if you’re using a platform with native Loop integration, commerce data is synced automatically. By syncing products, orders, customers, locations, inventory, and collections into Loop, you enable Loop to validate return eligibility, power exchange workflows, and maintain accurate records across your systems.

---

​

📦 API Reference

The Commerce Data APIs are organized into six main domains. Each API follows a consistent pattern with support for Create, List, Get, Update, Upsert, and Delete operations.

---

​

🛍️ Products API

The Products API provides Loop with standardized product data from any eCommerce system, ensuring accurate return processing and exchange matching.

• Product Metadata — Unique product IDs, SKUs, names, descriptions, and vendor details
• Pricing & Classification — Price, product type, collections, and tags
• Identifiers — Barcodes and external references for cross-platform tracking
• Variants & Options — Attributes like colors, sizes, and associated variants
• Media & Assets — Product images for return experience consistency

This data allows Loop to validate return items, process exchanges accurately, and maintain catalog consistency across platforms. Product Variants are managed as sub-resources of products:

---

​

📋 Orders API

The Orders API provides a comprehensive view of transactional data from any eCommerce system, ensuring Loop has the necessary context to facilitate seamless return and exchange processing.

• Order Metadata — Unique order identifiers, status, and associated sales channels
• Customer Information — Buyer details, including contact information and external references
• Financial Details — Total price, applied discounts, tax calculations, and refund history
• Shipping & Fulfillment — Shipping addresses, carrier details, fulfillment statuses, and tracking numbers
• Line Items & Adjustments — Purchased products, pricing, applied discounts, duties, and refund eligibility

This data allows Loop to validate return eligibility, create returns, and help facilitate refunds, store credit, and exchanges efficiently across any platform. Key Order Fields:

• line_items — Array of purchased items, each referencing a product/variant
• fulfillments — Fulfillment data including status, tracking, and fulfilled line items
• refunds — Refund data for reconciliation
• shipping_address / billing_address — Customer address information

---

​

👤 Customers API

The Customers API stores essential customer data to support return validation and exchange processing across platforms.

• Customer Identity — Unique customer IDs, external references, and contact details
• Order & Return Context — Flexible tags for purchase history, return status, and customer segmentation
• Channel Association — Identifies where the customer was created or last interacted

Customers can be created independently or through the Orders API, making this collection flexible for managing return history and personalizing the return experience across platforms. Key Customer Fields:

• first_name / last_name — Customer name
• email — Email address
• phone — Phone number
• tags — Array of tags for customer segmentation

---

​

📍 Locations API

The Locations API provides Loop with a standardized view of return and fulfillment locations, ensuring accurate routing and inventory management.

• Location Metadata — Unique location IDs, external references, and status
• Physical Address — Warehouse or store details, including company name and full address
• Channel Association — Identifies where the location is sourced from

This data enables efficient return routing, inventory restocking, and location-based return policies across platforms. Key Location Fields:

• name — Location name (e.g., “Main Warehouse”)
• status — active or inactive
• address — Full address object with address1, city, region, postal_code, country_code

---

​

📊 Inventories API

The Inventories API provides real-time visibility into stock levels across locations, ensuring accurate return processing and exchange fulfillment.

• Stock Availability — Tracks available inventory counts for product variants
• Product Details — SKU, barcode, name, and weight for precise identification
• Location Association — Links inventory to specific warehouses or return locations

This data helps prevent overselling, streamline restocking, and ensure exchange availability across platforms. Key Inventory Fields:

• available_count — Number of units available at the specified location

---

​

🏷️ Collections API

The Collections API organizes products into logical groupings, helping Loop maintain structured catalog data for returns and exchanges.

• Collection Metadata — Unique collection IDs, external references, and names
• Associated Products — SKUs, names, and external references for grouped items
• Channel Association — Identifies where the collection data originates

This data ensures consistent product categorization, enabling efficient return policies and exchange logic across platforms.

---

​

📤 Bulk Operations API

The Bulk Operations API lets you submit large batches of Create, Update, Upsert, and Delete operations across Orders, Products, Product Variants, Collections, and Inventory in a single request, instead of making individual calls for each record.

• Batch Processing — Submit a single JSONL file where each line is an independent job (type, parameters, payload)
• Cross-Resource Support — Works across Orders, Products, Product Variants, Collections, and Inventory using the same job payloads as their individual endpoints
• Async Execution & Status Tracking — Jobs run asynchronously; poll the bulk operation or its jobs list for pending, successful, and failed counts

This is especially useful for historical backfills and large batch syncs where making one API call per record isn’t practical. Supported Job Types:

• Orders — order_create, order_update, order_upsert, order_delete
• Products — product_create, product_update, product_upsert, product_delete
• Product Variants — product_variant_create, product_variant_update, product_variant_upsert, product_variant_delete
• Collections — collection_create, collection_update, collection_upsert, collection_delete
• Inventory — inventory_upsert, inventory_delete

---

​

⚠️ Technical Considerations

When integrating with the Commerce Data APIs, keep these critical implementation details in mind:

---

​

🔄 Common Sync Patterns

​

🗄️ Initial Data Sync (Historical Backfill)

When onboarding, you’ll typically sync data in this order:

​

⚡ Real-Time Sync

For ongoing operations, set up event-driven syncs to keep Loop updated:

• New Orders — Push to Loop when an order is placed
• Product Updates — Sync when products are created, updated, or discontinued
• Inventory Changes — Update stock levels after sales, returns, or restocks
• Order Status Changes — Update fulfillment status, refunds, and cancellations

---

​

✅ Conclusion

The Commerce Data APIs provide the foundation for integrating Loop with any commerce platform. By syncing your products, orders, customers, locations, inventory, and collections, you enable Loop to accurately validate returns, power exchange workflows, and maintain data consistency across your systems. Whether you’re performing a one-time historical backfill or building real-time sync pipelines, these APIs give you the flexibility to keep Loop in sync with your source of truth.