An AI agent between Shopify and an ERP is not a chatbot parked on the storefront. It is a piece of software with a trigger, a short list of records it may read, a decision it is allowed to make, and an action it may take. If any of those four are missing, you have a demo.

What starts the agent?

Something already happening in your systems. A refund ticket is opened. A paid order has been waiting in a queue. A delivery exception arrives from the warehouse. The trigger is an event with an identifier, not a person pasting a paragraph into a box and hoping the model remembers your business.

What is it allowed to read?

Name the records. For a refund, that is usually the Shopify order, the written policy, and the history of earlier refunds or replacements. The agent should not be able to browse the ERP because a prompt said 'look up the customer'. Retrieval is a query with an order id. The answer is data, which the decision step then has to use.

What does a decision look like?

A structured result. Eligible, refuse, or review. The reason should point at the rule, not at a paragraph of confidence. Eligible can start an action: a Shopify refund and, if your finance process requires it, a credit note in the ERP. Review means a person gets the same context the agent saw. Refuse means the action is not called.

  • Trigger: a ticket or an order event with an id.
  • Retrieve: order, policy, history. Nothing else.
  • Decide: eligible, refuse, or review.
  • Act: only the tools named for an eligible decision.

What is this not?

It is not a promise that support headcount falls by a percentage. That number does not exist until you measure your own queue, and this article will not invent one. It is also not a reason to skip the integration work. Webhook signatures, retries, and idempotency still decide whether the refund happens once.

If you are deciding whether a widget is enough, ask one question: does this need to change a record in Shopify or the ERP? If the answer is yes, you are specifying an agent and an integration, not installing a chat bubble.

Questions

Does the agent replace the integration?

No. The integration still moves the order and verifies the webhook. The agent decides whether a particular action, such as a refund, is allowed.

What should the agent do when the policy is ambiguous?

Stop and hand the case to a person, with the order, the policy clause, and the history it retrieved.