What the documents look like
Regional dealer stock replenishment sits in the wholesale and dealer channel as a daily rolling order flow, separate from seasonal centralized ordering events. The working material comes from dealer ERP records, brand ordering systems, warehouse inventory, and sales collections. Day-to-day paperwork covers replenishment requests, inventory turnover sheets, outbound delivery notes, and collection plans. This page addresses only model connection and configuration for product and marketing copy drafting. It does not cover business identity verification or report analysis.
For copy drafting, the model capability must be checked against the actual input. Where a replenishment request carries product images, the language model needs image input support. Where fields must be extracted from an inventory turnover sheet, the model needs tool choice or function call support. Model parameters are set in the application or node configuration. A same-named field on a compatible chat interface does not overwrite orchestration settings.
AI Proxy is a required dependency. The App service and any Admin service that reuses App or service configuration must set AIPROXY_API_ENDPOINT and a non-empty AIPROXY_API_TOKEN. Missing either one causes startup validation to fail. Legacy OpenAI environment variables and single-model custom request addresses do not replace these two settings.
Constraints at the model connections step
The following hypothetical drill sample is used throughout this page. It is a paper case, not a real customer record.
Material text for checking: "This batch replenishment request covers 200 cases of Product A, request date 2026-10-14, corresponding outbound delivery note CK-20261014-001, collection plan agreed for settlement before 2026-11-30."
Draft sentence to be assessed: "All replenishment requests from this dealer were delivered outbound on 2026-10-14."
The subject required for judgment is "this batch replenishment request." The object is "200 cases of Product A." The stated status is "request date 2026-10-14." The valid scope is "outbound delivery note CK-20261014-001." The draft sentence widens "this batch" to "all," and treats "request" as equivalent to "delivered outbound." The material does not state the full range of replenishment requests, and it does not state that outbound delivery was completed.
A second check concerns the collection plan. The material states an agreed settlement date of 2026-11-30. It does not state that payment was received. A draft sentence that presents the planned date as settled payment exceeds the material.
A third check concerns model connection itself. The endpoint value and token value are compared against the actual server configuration. These are configuration checks, not content checks.
Configuration and implementation checks
| Configuration item | Hypothetical starting value for this drill | How to check |
|---|---|---|
AIPROXY_API_ENDPOINT | AI Proxy service root address, no /v1 suffix | Compare against the deployed service address and confirm no path suffix |
AIPROXY_API_TOKEN | Non-empty administrator token matching the server | Confirm non-empty and matching the AI Proxy configuration |
| Language model image input | Checked against whether the replenishment request carries product images | Inspect the model metadata vision field |
| Tool choice or function call | Checked against whether fields must be extracted from the inventory turnover sheet | Inspect the toolChoice or functionCall field |
| Model mapping | For example, gpt-4o-test mapped to gpt-4o | Confirm the model ID matches the channel model |
| Channel priority | Range 1 to 100, higher value selected first | Compare against the actual channel configuration |
The starting values above are drill inputs chosen to make the comparison concrete. They are not official defaults.
Three common errors
- Drafting "this batch replenishment request" as "all replenishment requests." The material states only that this batch covers 200 cases of Product A. It does not state the full request range. Check input: material text and draft sentence. Compare: whether the subject scope matches. Observable result: if the draft widens a limited scope to all, the sentence is unsupported.
- Treating "request date" as "delivered outbound." The material states a request date of 2026-10-14 and an outbound delivery note number. It does not state outbound completion. Check input: material text and draft sentence. Compare: whether the status field matches. Observable result: if the draft presents a request state as completed outbound delivery, the sentence is unsupported.
- Treating the agreed collection date as received payment. The material states a collection plan agreed for settlement before 2026-11-30. It does not state actual payment. Check input: material text and draft sentence. Compare: whether the collection status matches. Observable result: if the draft presents a planned date as settled, the sentence is unsupported and the evidence gap remains.
How to verify the setup
- For the drill sample draft sentence "All replenishment requests from this dealer were delivered outbound on 2026-10-14," input the material text. Compare the subject scope "this batch" against "all," and the status "request" against "delivered outbound." If the draft exceeds the stated scope, mark it unsupported and record the evidence gap. Do not treat the gap as a contradiction.
- For the collection plan, input the material text "collection plan agreed for settlement before 2026-11-30." Compare whether the draft presents the planned date as settled. If the material does not state actual payment, mark the item as pending verification. Do not present it as completed.
- For the model configuration, input the hypothetical
AIPROXY_API_ENDPOINTandAIPROXY_API_TOKENvalues. Compare whether they match the server configuration and are non-empty. If either is missing or empty, startup validation fails. Check the values again before re-running verification.
Retrieval relevance does not act as a permission or entity filter. A similarity score does not exclude unrelated businesses or unauthorized records. Retrieval is not authorization. Where a check requires material outside the accessible retrieval scope, record the gap rather than inferring a result.