What the documents look like
For procurement in On-demand retail fulfillment, this page examines FastGPT vector indexes. Inspect the separate evidence for one pick, supplier stock and replenishment-request stages. The examples are hypothetical.
Constraints at the vector indexes step
A proposed instant-retail shortage note says the specified variant was not found during this pick. A purchase request separately records a saved replenishment draft that has not been sent. The first is a picking observation; the second is a request stage. Neither supplies supplier stock or a physical store count. Test indexes with questions about finding the item, sending replenishment and available supply, tracing each to its own evidence. A missing item during one pick does not establish a supplier shortage, and an indexed draft does not establish request acceptance.
Configuration and implementation checks
| Implementation check | Material in this test | Evidence action |
|---|---|---|
| Observation scope | Variant not found in this pick | Do not extend this to supplier stock. |
| Request stage | Draft saved but unsent | A hit does not establish acceptance. |
| Record time | Pre-send draft and later acknowledgment | Check the target and cited time. |
| Store object | Same-name goods may span stores | Preserve variant and location in retests. |
| New records | Counts, acknowledgments and receipts differ | Each supports its own status. |
Documented conditions
| Documented item / implementation check | Condition |
|---|---|
Embedding model | Knowledge bases associated with one search node must use the same embedding model. |
Original data and indexes | One original data block can have multiple indexes. |
Index content | Index wording should be complete and focused. |
Image indexes | Where image retrieval is used, inspect descriptions or image vectors. |
Version and result check | After a change, reuse questions to compare originals. |
Three common errors
- If one unsuccessful pick becomes zero stock across the store, inspect observation scope and count evidence. This picking note supplies no store-wide quantity.
- If that observation also becomes supplier unavailability, inspect the supplier evidence actually cited. One store record cannot establish both parties’ states.
- If drafts and a post-send receipt acknowledgment are mixed, inspect target and time. Receipt is distinct from acceptance or approval, and refreshing an index establishes no sending event.
How to verify the setup
When a receipt, stock count or procurement record becomes available, identify the event it actually supports before adding it as evidence. For a procurement response, distinguish receipt, acceptance and approval. Repeat the same variant-and-store questions. Inspect targets that may still point to the old draft and returns concerning another store’s same-name product. Verify the vector-model condition before linking store and procurement collections. For photographs, inspect specification markings through the actual text or image-processing route; file presence alone establishes no successful reading. Preserve absent supplier confirmation as a gap. Retrieving supplied material does not count live stock, submit orders or promise immediate arrival.
| Material context | Scope |
|---|---|
| Document types | Instant Order, Picking List, Out-of-Stock Report and Delivery Exception Order |
| Candidate sources | Douyin Instant Retail, Meituan or JD Daojia Backend, Store Inventory and Rider Tracking |
| Technical baseline | FastGPT v4.17.2 |