# Packing Slip vs. Received Count Log

> Reusable prompt turning packing slip lines and received counts into a discrepancy log, separating arithmetic differences from items needing a recount.

## Install

Copy the content below into your project:

# Packing Slip vs. Received Count Log

Reusable prompt turning packing slip lines and received counts into a discrepancy log, separating arithmetic differences from items needing a recount.

## Start here

Paste two text blocks into any ordinary AI chat that accepts text: **Block A**, your packing slip lines (item name, SKU or reference if present, slip quantity), and **Block B**, your received counts (item name, SKU or reference if present, counted quantity, plus any note such as "pallet arrived open" or "carton crushed"). Then paste the full prompt. The model replies with five sections: a summary line, a discrepancy table, a recount checklist, direct questions, and a list of assumptions and gaps.

## What this produces

The prompt builds a **draft discrepancy log** — nothing more. Each row is classified as MATCH, SHORT, OVER, or UNVERIFIED, and nonzero rows get a RECOUNT-REQUIRED or RECOUNT-OPTIONAL recommendation. It will not guess cause, fault, credit or next business action, and it never changes a count to make totals balance.

## How to check the output

- Do the arithmetic yourself on three rows: counted minus slip. The prompt asks for exactly this recheck.
- Compare the number of input lines with the number of table rows. Unmatched items must appear as UNMATCHED — PACKING SLIP ONLY or UNMATCHED — RECEIVED ONLY, never silently dropped.
- Make sure Section 3 lists only items that need a physical recount, most negative difference first.
- Read Section 3 before handing it to a warehouse colleague; the prompt requires wording that implies no blame.

## Prerequisites and limits

No installation, terminal or API is needed. You only need both blocks of text. Source reviewed; runtime not tested. If you paste one messy list, the prompt asks you to separate it and treats unlabeled numbers as unusable. It asks at most five clarifying questions, placed in Section 4. It cannot count anything itself, contact a supplier or carrier, file a claim, or change inventory records. Every Section 3 item still needs a person to physically recount it.

## FAQ

**Does it decide who is at fault for a shortage?** No. It only states the count situation and the recount recommendation; cause, liability and business action are outside its scope.

**What if one block is missing?** It returns only Section 4 with the questions needed to proceed, instead of inventing numbers.

## Source and thanks

Original TokRepo prompt, CC BY 4.0. External reference material retains its own rights. Reference context: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>). Fictional example only; no runtime test was performed.

## Complete reusable prompt

You are helping me reconcile a delivery against its packing slip. I will paste two blocks of text: (A) packing slip lines and (B) received counts. Your job is to build a discrepancy log, not to decide what happened or what anyone owes.

INPUT I WILL PROVIDE
Block A — packing slip, one item per line: item name, SKU or reference if present, slip quantity.
Block B — received counts, one item per line: item name, SKU or reference if present, counted quantity, and any note I include (for example "pallet arrived open", "counted by two people", "box crushed").
If I paste everything as one messy list, ask me to separate it or treat unlabeled numbers as unusable.

WHAT TO DO
1. Match Block A and Block B on SKU/reference first, then on item name. State the matching key you used per row.
2. For each matched item, compute difference = counted quantity minus slip quantity. Do the arithmetic only from the numbers I gave; never adjust a number to make totals agree.
3. Classify each matched row into exactly one status: MATCH (difference 0), SHORT (difference negative), OVER (difference positive), or UNVERIFIED (missing count, duplicate line, unit mismatch like boxes vs. units, or a name match you are unsure about).
4. For every SHORT, OVER or UNVERIFIED row, assign a recount recommendation: RECOUNT-REQUIRED or RECOUNT-OPTIONAL. Use RECOUNT-REQUIRED when the difference is nonzero, when the count is missing, when duplicate lines exist for the same SKU, or when my note says the packaging was damaged. Use RECOUNT-OPTIONAL only for zero-difference rows where the match key was a fuzzy name match. Never mark a nonzero difference as closed.
5. List items appearing in only one block under UNMATCHED — PACKING SLIP ONLY or UNMATCHED — RECEIVED ONLY. Never silently drop them and never merge them into a matched row.
6. Do not infer cause, fault, value, credit, or next business action. You may only state the count situation and the recount recommendation.

OUTPUT FORMAT
Section 1 — Summary line: total slip lines, total received lines, count of MATCH / SHORT / OVER / UNVERIFIED / unmatched.
Section 2 — Discrepancy table, Markdown, columns: Item | SKU/Ref | Slip Qty | Counted Qty | Difference | Match Key Used | Status | Recount Recommendation | My Note.
Section 3 — Items requiring a human recount, as a plain checklist, most negative difference first, then UNVERIFIED, then OVER. Each line: item, difference or reason, and the single physical check to perform (for example "recount the two cartons labelled X").
Section 4 — Items I must confirm before you can finish, phrased as direct questions (for example "Block B lists SKU 4471 twice — should both lines be summed or is one a duplicate?").
Section 5 — Assumptions and gaps: every assumption you made about matching or units, and every value you could not compute.

UNCERTAINTY AND MISSING INPUT
Ask at most five clarifying questions total, placed in Section 4; do not stall the whole output waiting for answers. Where a number is missing, write "MISSING" rather than estimating. If Block A or Block B is absent, produce only Section 4 with the questions needed to proceed.

REVIEW CHECKS BEFORE I USE THIS
- Re-add slip minus counted for three rows yourself, show the recheck, and correct any row that does not reconcile.
- Confirm no row was dropped between the input blocks and the table; compare line counts explicitly.
- Confirm no status was assigned from context or assumption, only from the supplied numbers and the stated rules.
- Confirm Section 3 is safe for me to hand to a warehouse colleague without implying blame.

BOUNDARIES
This produces a draft discrepancy log for human review. It does not contact a supplier or carrier, does not file a claim, does not modify inventory records, does not schedule anything, and cannot verify a count on its own. A person must physically recount every item in Section 3 before any shortage is treated as real.

WORKED EXAMPLE (fictional, for shape only)
Input A: Widget A / SKU 4471 / 12; Bracket B / SKU 5530 / 8; Tape roll / 40
Input B: Widget A / SKU 4471 / 10; Bracket B / SKU 5530 / 8; Tape roll / 40, note "carton crushed"; Cable tie / SKU 9002 / 100
Expected shape: table shows Widget A SHORT -2, RECOUNT-REQUIRED; Bracket B MATCH 0, RECOUNT-OPTIONAL if name-matched; Tape roll UNVERIFIED if the note makes the count questionable; Cable tie under UNMATCHED — RECEIVED ONLY. Section 3 lists Widget A first. Section 4 asks whether the crushed-carton tape count should be redone and whether Cable tie was on the slip under another name.

PASS/FAIL CHECKS ON THE EXAMPLE
Pass if: every arithmetic difference is correct; Cable tie is never merged into a slip row; no cause or liability is stated; Section 3 exists and lists only rows needing physical action.
Fail if: any count is changed to balance totals; a status is invented for the unmatched cable tie; a supplier or claim action is recommended; the crushed-carton note is ignored.

Now ask me for Block A and Block B if I have not pasted them, then produce the sections above.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 装箱单与实收数量差异日志

可复用的提示词，把装箱单明细与实收数量整理成差异日志，将算术差异与需要人工复点的项目分开记录。

## 开始使用

在任意一个可接受文本的普通 AI 对话中粘贴两段文本：**Block A**，你的装箱单明细（物料名称，如有则含 SKU 或参考号，以及装箱数量）；**Block B**，你的实收数量（物料名称，如有则含 SKU 或参考号，实点数量，以及你附加的备注，例如“托盘到货时已开封”“箱子被压扁”）。然后粘贴完整提示词。模型会回复五个部分：汇总行、差异表、复点清单、直接问题，以及假设与缺口清单。

## 产出内容

该提示词只生成一份**差异日志草稿**，仅此而已。每一行被归类为 MATCH、SHORT、OVER 或 UNVERIFIED，非零差异行会给出 RECOUNT-REQUIRED 或 RECOUNT-OPTIONAL 建议。它不会推测原因、责任、赔付或后续业务动作，也绝不会为了凑平总数而改动任何数量。

## 如何检查输出

- 自己动手验算三行：实点数量减装箱数量。提示词本身就要求做这项复核。
- 对比输入行数与表格行数。未匹配的物料必须出现在 UNMATCHED — PACKING SLIP ONLY 或 UNMATCHED — RECEIVED ONLY 下，不得被悄悄丢弃。
- 确认第 3 部分只列需要实物复点的物料，且负数差异最大的排在前面。
- 交给仓库同事之前先读一遍第 3 部分；提示词要求措辞中不隐含任何指责。

## 前提与限制

无需安装、终端或 API，只需要这两段文本。已审阅来源；未做运行测试。如果你把内容粘成一团乱列表，提示词会要求你先分开，并把没有标注的数字视为不可用。它最多提出五个澄清问题，放在第 4 部分。它自身无法清点任何东西，不会联系供应商或承运商，不会提交索赔，也不会改动库存记录。第 3 部分中的每一项仍须由人工实物复点。

## 常见问题

**它会认定短少的责任方吗？** 不会。它只陈述数量情况和复点建议；原因、责任与业务动作不在其范围内。

**如果缺少其中一段文本怎么办？** 它只会返回第 4 部分及继续进行所需的问题，而不会凭空编造数字。

## 来源与致谢

TokRepo 原创提示词，CC BY 4.0。外部参考资料保留其自身权利。参考背景：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)。示例为虚构，仅用于说明格式；未执行运行测试。

## 完整可复制提示词

你正在帮助我将一次到货与其装箱单进行核对。我会粘贴两段文本：(A) 装箱单明细和 (B) 实收数量。你的任务是建立一份差异日志，而不是判断发生了什么或谁欠谁什么。

我将提供的输入
Block A — 装箱单，每行一项：物料名称，如有则含 SKU 或参考号，装箱数量。
Block B — 实收数量，每行一项：物料名称，如有则含 SKU 或参考号，实点数量，以及我提供的任何备注（例如“托盘到货时已开封”“由两人点数”“箱子被压扁”）。
如果我把所有内容粘成一团乱列表，请要求我先分开，或把没有标注的数字视为不可用。

要做什么
1. 先按 SKU/参考号匹配 Block A 与 Block B，再按物料名称匹配。逐行说明你使用的匹配键。
2. 对每个匹配的物料，计算差异 = 实点数量减装箱数量。只根据我给出的数字计算；绝不为了凑平总数而调整数字。
3. 将每个匹配行归类为且仅归为一类状态：MATCH（差异为 0）、SHORT（差异为负）、OVER（差异为正）或 UNVERIFIED（缺少数量、重复行、单位不一致如箱与件、或你对名称匹配没有把握）。
4. 对每个 SHORT、OVER 或 UNVERIFIED 行，给出复点建议：RECOUNT-REQUIRED 或 RECOUNT-OPTIONAL。当差异非零、数量缺失、同一 SKU 存在重复行，或我的备注说明包装受损时，使用 RECOUNT-REQUIRED。仅对匹配键为模糊名称匹配的零差异行使用 RECOUNT-OPTIONAL。绝不将非零差异标记为已结案。
5. 仅出现在一个块中的物料，列在 UNMATCHED — PACKING SLIP ONLY 或 UNMATCHED — RECEIVED ONLY 下。绝不悄悄丢弃，也绝不合并进匹配行。
6. 不要推断原因、责任、价值、赔付或后续业务动作。你只能陈述数量情况和复点建议。

输出格式
第 1 部分 — 汇总行：装箱单总行数、实收总行数、MATCH / SHORT / OVER / UNVERIFIED / 未匹配的计数。
第 2 部分 — 差异表，Markdown，列：Item | SKU/Ref | Slip Qty | Counted Qty | Difference | Match Key Used | Status | Recount Recommendation | My Note。
第 3 部分 — 需要人工复点的物料，以纯清单形式呈现，负数差异最大的排在前面，然后是 UNVERIFIED，然后是 OVER。每行：物料、差异或原因，以及要执行的一项实物检查（例如“复点标有 X 的两个箱子”）。
第 4 部分 — 你必须先确认我才能完成的事项，以直接问题的形式提出（例如“Block B 两次列出 SKU 4471 — 两行应相加，还是其中一行是重复？”）。
第 5 部分 — 假设与缺口：你对匹配或单位所做的每一项假设，以及你无法计算的每一个值。

不确定性与缺失输入
总共最多提出五个澄清问题，放在第 4 部分；不要为了等待答案而停滞整个输出。数量缺失处写“MISSING”，不要估计。如果 Block A 或 Block B 缺失，只输出第 4 部分及继续进行所需的问题。

我使用前的复核检查
- 自己重新把三行的装箱数量减实点数量相加，展示复核过程，并修正任何对不上账的行。
- 确认输入块与表格之间没有任何行被丢弃；明确比较行数。
- 确认没有任何状态来自上下文或假设，只来自提供的数字和所述规则。
- 确认第 3 部分可以安全交给我给仓库同事，且不隐含指责。

边界
这会生成一份供人工复核的差异日志草稿。它不会联系供应商或承运商，不会提交索赔，不会改动库存记录，不会安排任何事项，也无法自行核实数量。在对任何短少认定为真实之前，必须由人工对第 3 部分中的每一项进行实物复点。

示例（虚构，仅用于展示格式）
输入 A：Widget A / SKU 4471 / 12；Bracket B / SKU 5530 / 8；胶带卷 / 40
输入 B：Widget A / SKU 4471 / 10；Bracket B / SKU 5530 / 8；胶带卷 / 40，备注“箱子被压扁”；扎带 / SKU 9002 / 100
预期格式：表格显示 Widget A SHORT -2，RECOUNT-REQUIRED；Bracket B MATCH 0，若按名称匹配则 RECOUNT-OPTIONAL；若备注使数量存疑，则胶带卷为 UNVERIFIED；扎带归入 UNMATCHED — RECEIVED ONLY。第 3 部分先列出 Widget A。第 4 部分询问被压扁纸箱中的胶带数量是否需要重新清点，以及扎带是否以其他名称出现在装箱单上。

对示例的通过/不通过检查
通过条件：每个算术差值都正确；扎带从未被并入装箱单行；未陈述原因或责任；第 3 部分存在且只列出需要实物处理的行。
不通过条件：为凑平总数而改动任何数量；为未匹配的扎带编造状态；建议供应商或索赔动作；忽略纸箱被压扁的备注。

如果我没有粘贴 Block A 和 Block B，现在就向我索要，然后生成上述各部分。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/packing-slip-vs-received-count-log-3e1238a5
Author: Prompt Lab