Skip to main content

Integrations

Pinch reads and writes data across four families of platforms. Most of these are wired up during white-glove onboarding — this page is for understanding what connects to what.

Order sources​

Where your orders, returns, and customer data come from. Three options — pick one. Most Pinch merchants run on one of the platform integrations; the REST API is the path for any custom stack.

Returns management (RMS)​

Where your customer initiates a return. Pinch reads return events from your RMS and writes the decision (Allow / Deny / Review) back as an customer tag your RMS can act on.

If your RMS isn't listed, email support@pinch.ai. New RMS integrations are commonly added as one-off setups.

Customer support​

Where your support team works. Pinch surfaces customer risk inside support tickets and sends transactional emails through your support tool's outbound infrastructure.

How decisions flow back​

In a typical Shopify deployment, your stack sees Pinch like this:

  1. A customer places an order. Shopify notifies Pinch.
  2. A few days later, the customer initiates a return through your RMS. The RMS notifies Pinch.
  3. Pinch evaluates the return and writes an customer tag like Pinch - Review : Suspect Abuse onto the Shopify order.
  4. Your RMS reads the tag and routes the return accordingly — auto-approve, route to manual review, or deny.
  5. Your warehouse inspects the returned item. The disposition (NEW, EMPTY_BOX, etc.) flows back to Pinch.
  6. Your support tool (Dixa / Gorgias) sees the customer's Pinch Assessment when a ticket is opened.

Everything in steps 1–6 is configured during onboarding. You don't need to wire it up yourself.