Reference · built on requestConnectorCommerce & orders

commercetools

Orders, customers, products, and inventory entries from a commercetools Project, with Subscriptions pushing changes to your queue.

Request accessPricing ↗

About

commercetools is a headless commerce platform. Everything belongs to a Project served from a regional host such as api.europe-west1.gcp.commercetools.com or api.us-central1.gcp.commercetools.com. The HTTP API covers carts, orders, payments, customers, products and product projections, inventory, stores, channels, and shipping methods. Subscriptions send a Message, a change notice, or an Event to a queue you own when a resource changes.

Through Fibric, an operator reads orders by state, watches OrderStateChanged and OrderShipmentStateChanged messages, and proposes update actions on the order or an inventory entry. You approve; the receipt shows the action, the reason, and the reverse action.

This is a reference listing. It documents what Fibric would read from commercetools and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Orders with orderState, shipmentState, paymentState, lineItems, shippingInfo, returnInfo, and syncInfo
  • Order messages such as OrderCreated, OrderStateChanged, OrderShipmentStateChanged, OrderPaymentStateChanged, DeliveryAdded, and ParcelTrackingDataUpdated
  • Customers and customer groups, and carts before they become orders
  • InventoryEntry records per sku and supplyChannel with quantityOnStock, availableQuantity, restockableInDays, and expectedDelivery
  • Change notifications for created, updated, and deleted resources through a Subscription
  • Products, product projections, stores, channels, and shipping methods

Proposed actions

  • Target capability: propose changeOrderState, changeShipmentState, or changePaymentState on an order
  • Target capability: propose addDelivery, addParcelToDelivery, or setDeliveryItems to record what shipped
  • Target capability: propose addReturnInfo and setReturnShipmentState when goods come back
  • Target capability: propose addQuantity, removeQuantity, or changeQuantity on an InventoryEntry
  • Target capability: propose setCustomField or transitionState on an order for your own workflow

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Ship confirmation that writes itself back

    Take the carrier event, then propose addDelivery and addParcelToDelivery with tracking data so shipmentState moves to Shipped.

    With Tracking Sync, Split Shipment

  • Stop a Confirmed order that should not go out

    On OrderCreated, check the customer and address against past orders and propose changeOrderState to Cancelled before the warehouse picks.

    With Order Risk, Duplicate Order

  • Return goods to stock with a record

    When a return arrives, propose addReturnInfo and then addQuantity on the matching InventoryEntry, both for approval.

    With Returns Triage, Return Restock

  • Hear about backorders as they happen

    Subscribe to OrderShipmentStateChanged and draft the customer notice when a line goes to Backorder or Delayed.

    With Backorder Notice, Promise Date

Requirements

  • A commercetools Project and its region; the auth and API hosts differ by region, for example auth.us-central1.gcp.commercetools.com
  • An API Client whose scopes cover the work, for example manage_orders:{projectKey} and manage_customers:{projectKey}
  • A queue you own for Subscriptions: AWS SQS, SNS, or EventBridge, Azure Service Bus or Event Grid, Google Cloud Pub/Sub, or Confluent Cloud
Authentication
OAuth 2.0 client credentials: an API Client from the Merchant Center posts to {auth_host}/oauth/token with grant_type=client_credentials and receives a bearer token that expires after 48 hours.

Limits

  • A Project allows 50 Subscriptions by default; raising it needs a performance review
  • Subscription delivery is at least once, unordered, and can lag by minutes; retries stop after 48 hours
  • Queries return up to 500 results per page and an offset no higher than 10000
  • One update request may carry at most 500 update actions

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request commercetools ↗

Questions and answers

How does commercetools push changes to Fibric?
Through Subscriptions. Each one names a destination you own: AWS SQS, SNS, or EventBridge, Azure Service Bus or Event Grid, Google Cloud Pub/Sub, or Confluent Cloud. Payloads are a predefined Message, a change notice for created, updated, or deleted resources, or an Event. Delivery is at least once with no ordering guarantee.
Which states can an order be in?
orderState is Open, Confirmed, Complete, or Cancelled. shipmentState is Shipped, Ready, Pending, Delayed, Partial, Backorder, or Delivered. paymentState is BalanceDue, Failed, Pending, CreditOwed, or Paid. Each is changed with its own update action: changeOrderState, changeShipmentState, changePaymentState.
How long does an access token last?
An access token from the client credentials flow expires after 48 hours. The connector requests a new one from the regional auth host, for example auth.europe-west1.gcp.commercetools.com, using the API Client's client_id and client_secret. Tokens go in the Authorization: Bearer header, never in the URL.
Ask about commercetools

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with commercetools through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy