Ciwi
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant

Handle order-change requests within permitted actions

A buyer asks to change an order that may already be packed, and the agent cannot see which actions are still allowed. In this case, the immediate task is to handle order-change requests within permitted actions. The workflow should produce a response that states what the order's current state permits and what outcome the change would produce.

Topic
Order and Shipping Customer Support
Target keyword
shopify order modification automation
Copyable AI prompt

A prompt you can drop directly into Spark

First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.

ai-prompt.txt
Act as a Shopify operations specialist.
Help me handle order-change requests within permitted actions.
My store context is [describe the business, products and target audience].

My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [the customer identity check against the order, the order record with its current fulfilment and payment state, the line items in scope, and the merchant's stated rule of permitted changes per order stage]. Judge the request against the order's current state rather than the state at purchase, name the action that state still permits and the outcome it produces including any price or shipping difference, and treat a request outside the stated rule as a refusal carrying a permitted alternative.
Return the support response and action plan for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.
Use in Spark
How to solve

A recommended resolution workflow

Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.

01

Step 1

Collect the customer identity check against the order, the order record with its current fulfilment and payment state, the line items in scope, and the merchant's stated rule listing which changes are permitted at each order stage.

02

Step 2

Judge the request against the order's current state rather than the state at purchase, name the action that state still permits and the outcome it produces including any price or shipping difference, and treat a request outside the stated rule as a refusal carrying a permitted alternative.

03

Step 3

Deliver the support response with the state and permitted action it relies on, verify each stated outcome against the supplied order records, and escalate to a named owner when the change touches payment or a shipment already handed to the carrier.

FAQ

Common questions when running this scenario

Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.

How is the request matched to the right order?

The customer is checked against the contact detail on the order and the order is confirmed by its identifier before anything is discussed, because a change applied to a lookalike order is hard to undo; where the identity check fails the request waits for a person instead of proceeding on a partial match.

Can an address still be changed after dispatch?

It depends on the stage the order has reached and the merchant's stated rule for that stage, so the answer names the current state first; once a shipment has been accepted by the carrier the order is normally out of reach, and the reply offers the option that state does allow rather than promising an edit.

What happens if the change alters the order total?

The new total with any price or shipping difference is stated and confirmed by the customer before anything is applied, because silently collecting a different amount is the complaint that follows; if the difference cannot be calculated from the records, the request goes to a person.

Related scenarios

Continue with adjacent or same-topic scenarios

Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.

Next step

Want these AI scenarios embedded directly into daily operations?

Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.

Open Spark product pageBack to Spark scenario library