What the documents look like
On a Shopify standalone store, the merchant configures payment, shipping and fulfillment services directly rather than relying on a platform to handle returns automatically. The working materials for this category are order details, shipping rate templates, shipping labels and refund records. These live across Shopify Admin, payment gateways, carrier systems and inventory location data. The update rhythm is per order or daily.
For the task of drafting product and marketing copy, those materials supply the facts a draft has to respect: product name, specifications, shipping scope, refund conditions. A copy sentence that promises a delivery window or a refund period has to trace back to one of these documents. This page covers only the model connection and configuration step behind that drafting work. It does not construct business features that the documents do not describe.
Constraints at the model connections step
Model access depends on AI Proxy. Both the App service and the Admin service must set AIPROXY_API_ENDPOINT and a non-empty AIPROXY_API_TOKEN. Missing either one causes startup validation to fail. Legacy OpenAI environment variables or a single-model custom request address cannot substitute for these two settings. When configuring a model channel, the proxy address field takes a BaseUrl, and the question of whether to append /v1 has to be checked rather than assumed. Model capabilities are verified against the inputs the application actually needs, with multimodal input and tool calling checked separately. Application parameters are set in the application or node configuration; a same-named field on a compatible chat interface is not assumed to override orchestration.
A hypothetical paper exercise sample follows. The source material reads: "Orders from this store are dispatched by the carrier within two business days after payment. Shipping fees are charged at the amount shown on the order checkout page. Refund requests must be submitted within seven days of delivery." The draft sentence under review reads: "This store promises same-day dispatch on all orders and supports no-reason refunds within thirty days of delivery." The check compares the draft sentence against the source on subject, period and field.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this exercise | How to check it |
|---|---|---|
| AIPROXYAPIENDPOINT | Fill in the service root address per the actual deployment | Confirm no /v1 or /chat/completions is appended |
| AIPROXYAPITOKEN | Fill in a non-empty token matching the server | Confirm non-empty and consistent with AI Proxy |
| Model channel proxy address | Fill in the BaseUrl | Confirm whether /v1 needs to be appended |
| Model capability | Check against the inputs the application needs | Verify multimodal and tool calling separately |
| Application parameters | Set in the application or node configuration | Confirm same-named fields do not override orchestration |
| Model status probing | Enable as needed, interval an integer from 5 to 60 minutes | Confirm only enabled models are probed |
The starting points come from documented required fields and optional ranges. They are not official defaults.
Three common errors
- Filling
AIPROXY_API_ENDPOINTwith a full model request address and appending/v1, which fails startup validation. Check whether the input is a service root address and whether a path is appended; observe the startup validation result. - Treating "same-day dispatch" in the draft sentence as equivalent to "within two business days after payment" in the source material. Check subject, period and field across the two; observe whether they agree.
- Treating "no-reason refunds within thirty days" in the draft sentence as the same period as "refund requests within seven days of delivery" in the source material. Check the period values across the two; observe whether they conflict.
How to verify the setup
- Input the hypothetical source material and the draft sentence. Compare "same-day dispatch" against "within two business days after payment." If the draft sentence does not state that period, record it as unsupported rather than as a denial.
- Input the hypothetical source material and the draft sentence. Compare "within thirty days" against "within seven days." If the two are mutually exclusive values on the same field, record a conflict.
- Input the hypothetical source material. Compare the refund request period against the refund period in the draft sentence. If the draft sentence does not state the submission condition, record an evidence gap and leave it pending verification.
These are paper checks. No test was executed, and no deployment or approval is claimed.