On the afternoon before a tote order is due to leave New York for production, Maya receives a supplier message: the approved canvas is unavailable, but a coated alternative can keep the date. Her team has approved the artwork. The supplier wants a quick yes. Maya needs to know whether that yes would authorize the same product, a new material, or an unresolved market review.
A merchandise request workbook gives her a place to make that decision. It ties one product to its material, quantity, destination market, accountable approver, proof version and acceptance condition. When an input changes, the workbook should expose the reopened decision instead of letting an old approval travel with a different product.
Use the workbook for one SKU and one market decision
Start a separate file for each SKU and market combination. A tote supplied to a US employee program and the same-looking tote supplied to a Taiwan event may share artwork, yet need different market evidence and responsible parties. A single worldwide “approved” cell would conceal those differences. Keep the shared design reference, but give each local release its own record.
The workbook contains five tabs: Readiness, Request, Specification, Market and Changes. Readiness is the output. The other tabs hold the inputs that make that output explainable. The file starts with an explicitly labeled worked example. Replace the example before using it for an actual request; an example owner or evidence description is not your team's completed approval.
The score counts five recorded prerequisites. It does not measure product safety, supplier quality or the probability of a successful delivery. A five-point file can still show HOLD when a specialist review or an open change remains unresolved. That distinction matters: completeness helps people review evidence, but it cannot turn incomplete legal or technical judgment into a certification.
Keep individual recipient addresses out of this file. A product decision needs destination-market information and an accountable program owner. It generally does not need the home addresses of everyone who might receive the item. Use the approved recipient-data workflow later, with the access and retention rules appropriate to that workflow.
| Prerequisite | What the file records | What must reopen it |
|---|---|---|
| Product definition | Product, material/components and positive whole-unit quantity | Changed product, material or quantity |
| Market evidence | Target market, review owner, evidence location and review version | Missing evidence or a revised market assessment |
| Accountable approver | Request ID, owner, approver, approval date and delivery window | Missing accountability or an unaccepted new request |
| Current proof acceptance | Current versus approved proof, market review, product, material, quantity and target market | Any mismatch between current inputs and the approved snapshot |
| Acceptance condition | A specific condition the team will check | An absent or inadequate receiving requirement |
Write a product definition someone else can inspect
“Canvas tote” is a purchasing category, not a sufficient specification. Record the material description you actually intend to buy, including relevant coatings, linings, handles, closures and components. Keep dimensions, construction and artwork details in the linked specification or proof. The workbook's short material cell should point reviewers toward that exact definition rather than summarize away a consequential component.
Enter quantity as a positive whole number of units. Zero is not an order ready for release, and a blank is not a zero. If a kit contains several independently supplied products, use separate SKU records for those products and a clearly identified kit assembly reference. Do not hide a battery, food item or child-directed component inside a generic “welcome kit” row.
Give the proof a stable version identifier. “Latest file” will change meaning, and a shared folder link may show a newer upload tomorrow. A useful record names the actual proof or specification revision and preserves its accepted predecessor. A team can choose its own version convention, provided the same convention appears in the supplier instruction and the approval evidence.
The approved product, material and quantity fields are snapshots, not convenient copies to refresh automatically. Change the current fields first. Compare them with the previously accepted values. Update the approved snapshot only after the appropriate person accepts the new version and the change log records the resolution. Otherwise the calculation would erase the very disagreement it is meant to reveal.
Do not treat a color swatch as evidence of material composition, or an artwork approval as permission to replace a physical component. If the supplier cannot substantiate the proposed material, leave its evidence open. A sensible next action may be another sample, a documented alternative, or a revised delivery plan rather than a hurried release.
Separate the market screen from the commercial approval
For a US request, first determine which product rules actually apply to the item and who owns that assessment. The US Consumer Product Safety Commission's general-use product guidance explains certification for general-use products subject to applicable consumer product safety rules. It also explains that a material change can affect compliance and may require retesting or an updated General Certificate of Conformity. Those are conditional responsibilities, not a rule that every promotional tote needs the same certificate.
Use that guidance to ask a precise question: does the proposed change affect any requirement applicable to this exact product? The workbook records the reviewer, evidence and conclusion. It is not a GCC, test report or classification service. A buyer's brand approval and a qualified market review may involve different people and different evidence, even when both concern the same material.
The Market tab includes a specialist-review flag and a separate clearance field. Enter an explicit reviewed decision. An empty specialist flag must not behave like “no specialist required.” Child-directed products, electrical components and other regulated or hazardous characteristics should move to an appropriately qualified reviewer; the workbook must not guess the outcome from a product name.
If a request spans other jurisdictions, obtain the local evidence for each actual route. Translating an American safety page into Korean does not establish the Korean rules for a power bank. Likewise, a familiar certification mark on a supplier photograph does not prove coverage for the exact model, factory, revision or intended market.
Keep commercial conditions visible alongside that review. The approver needs to know the accepted quantity and delivery window, and where price or ordering terms are recorded. A valid technical assessment cannot commit an unapproved budget. An approved budget cannot cure missing product evidence. The release decision needs both streams to reach the same current specification.
Worked decision one: accept the tote request, then reopen the coating change
Assume Maya's original request is for 500 adult-use cotton totes in one market, with proof V3, market review M1 and an agreed delivery window. These are worked assumptions, not market averages or a report of a customer order. The request owner, buyer approver, approval date and acceptance condition are recorded. The current product, cotton material and quantity match their approved snapshots.
The five prerequisite flags each return one. Their sum is five. The specialist assessment is explicitly recorded as not required for the reviewed scope, and the example change row is resolved. Readiness therefore displays READY, meaning the record can be sent to the next agreed production step. It does not promise that manufacturing or delivery has already occurred.
Now the supplier proposes coated fabric. Maya changes the current material cell and opens a change record, preserving the old cotton definition. The approved material remains cotton. The current-proof-acceptance flag drops to zero, so the score becomes four of five. The open change also keeps the final gate at HOLD. The original approval remains useful history without authorizing the substitute.
The next action is to obtain the replacement specification, update the proof where necessary and ask the market owner whether the new coating affects the earlier review. If that assessment changes, record M2 as the current market review. Updating the approved artwork alone cannot close the mismatch with the approved market-review version.
Maya can close the change only when the buyer accepts the new physical definition and any required review is resolved. The responsible person records the decision date and resolution in Changes, marks that change accepted, and updates the approved snapshots to the versions actually accepted. She should preserve the previous workbook file before making that update so the old basis remains recoverable.
If the new evidence cannot be obtained in time, HOLD is the useful answer. The team can choose the approved original material with a revised date, an independently accepted alternative, or a smaller scope. It should not manufacture a completed review merely because the supplier's production slot is about to close.
Worked decision two: increase quantity without silently changing the commitment
Consider a separate US event request for 500 identical pouches. The organizer asks for 600 after registrations rise. Assume the product, material, artwork and intended market remain unchanged. The increased quantity is a commercial change; it is not automatically a new material-change testing requirement. The team still needs to confirm what the increase does to price, capacity and the agreed delivery window.
Change the current quantity from 500 to 600 while leaving the approved quantity at 500. Four prerequisites remain recorded, but current proof acceptance becomes zero because the commercial snapshot no longer matches. The score is four and the gate is HOLD. This prevents a small-looking spreadsheet edit from silently increasing the approved order.
Add a change row that names the old and new quantity references, the responsible owner and the decision needed. The supplier should confirm whether the same material lot, process and physical specification will be used. The buyer checks the revised commercial terms and the delivery effect. If the increase also triggers a substitute component, it is no longer a quantity-only decision and must follow the material-change path.
Once the buyer accepts the revised commitment, record a dated resolution and update the approved quantity to 600. Keep the earlier accepted file and the new version distinct. When no other gate is open, the score returns to five and the final status can return to READY. The arithmetic documents the prerequisites; the supplier's written acceptance and buyer's decision substantiate the change.
If only 500 units can meet the original window, do not enter 600 and leave the old delivery statement in place. Choose an explicitly approved split, reduce the request or revise the window. For a split, identify the separate quantities and obligations in the acceptance evidence so receiving staff know what counts as a complete first delivery.
Read the score and the final gate together
Readiness adds five binary flags. Each flag is either one for a recorded prerequisite or zero for a missing or mismatched prerequisite. It is intentionally simple enough for a reviewer to follow. A zero does not estimate the severity of a problem, and five is not a percentage probability of successful fulfillment.
The final gate checks the score, the specialist decision and unresolved change rows. An entered change row needs an ID, old and new version references, change type, owner, numeric accepted date, accepted flag and resolution before its open-change flag becomes zero. A completely empty unused row is neutral. A partially completed row remains open even when its change ID is missing.
This means a five-point file can correctly remain HOLD. For example, the product and market fields may all be present while a specialist review is explicitly required but not accepted. Filling the clearance field without an actual reviewed decision would defeat the workflow; the workbook cannot authenticate the person typing into a cell.
Use file access and your team's approval policy to control who can edit approved snapshots. Keep the actual evidence in a stable approved repository, with the workbook pointing to the exact version. The file is a transparent coordination aid. It does not supply signatures, access controls, immutable storage or regulatory judgments simply because its formulas are visible.
| Input change to test | Expected result | Evidence the reviewer should inspect |
|---|---|---|
| Clear target market | Three prerequisites; HOLD | Both market evidence and approved-market matching are incomplete |
| Change material only | Four prerequisites; HOLD | Current material differs from approved material |
| Change quantity only | Four prerequisites; HOLD until accepted quantity matches | Revised commercial and delivery acceptance |
| Add an unresolved change ID | Five prerequisites may remain; HOLD | Open change flag equals one |
| Require specialist review without clearance | Five prerequisites may remain; HOLD | Named review and unresolved clearance |
| Remove supplier evidence location | Four prerequisites; HOLD | Missing market evidence location |
Make acceptance observable at receiving
An acceptance condition should name something the next person can check. “Good quality” does not tell a receiving team whether a shipment matches the agreed proof. Refer to the accepted physical sample or specification, approved artwork version, quantity and reviewed labeling evidence. Keep the detailed inspection method and any sampling agreement in the linked evidence rather than inventing a universal acceptance percentage.
For the tote example, the receiving owner might compare the delivered material and construction with the accepted sample, verify the artwork against V3 or its accepted successor, count the units and check the agreed label reference. These are examples of observable checks, not an exhaustive safety inspection or an assertion that every shipment can be fully inspected at receipt.
Record who handles discrepancies before the order is released. If a different material arrives, preserve photographs, packaging and the relevant product references, identify the affected units, and ask the designated owner to assess the next step. Do not overwrite the current material field to make the delivered substitute appear to have been approved earlier.
Separate an operational receipt from acceptance of a deviation. Warehouse staff may acknowledge that boxes arrived without approving a changed component. The buyer or qualified reviewer named in the change process decides whether a deviation can be accepted, needs rework or requires another action. Keep that decision attached to a new change record and preserve its relationship to the original request.
Pilot the file before using it as a release instruction
Use the editable XLSX as the working record. Keep the readiness formulas intact and enter changes in the amber input cells. Before the first live request, save a copy with a meaningful request ID and replace every worked-example value, including the evidence description, people, date and acceptance condition. The example is deliberately complete to demonstrate the calculation; its displayed result does not authorize your order.
When handing the file to another team, include the exact specification and evidence references it names. Check that the receiving reviewer can open those references under the agreed access settings. A link that works only for the author is an incomplete handoff. Preserve the original accepted file alongside later revisions, and identify which version is the current instruction in the order communication. Avoid circulating several attachments all named “final.”
Test one real SKU with the people who will use the record. Ask the request owner to enter the current product, the market reviewer to supply the exact evidence reference and the approver to explain which proof they accepted. Have a second person read the output without asking the author to translate every cell. An unexplained READY result is a reason to inspect the inputs, not to skip the pilot.
Then deliberately clear the market, change the material, increase quantity and add an open change ID. Confirm that each relevant output changes and that restoring an input does not erase the change history. Use a disposable copy for these tests. Restore the actual approved values before circulating the working file, and keep the dated test evidence separately.
Check the file in the spreadsheet application your team will use. The formulas use ordinary scalar logic, but a rendered preview cannot establish every application's editing behavior. Treat a downloaded copy with missing formulas, broken references or stale calculations as a failed handoff. Recalculate and inspect the output after changing an input; seeing the original example result alone proves very little.
Keep a refresh owner for the template. Review it when the fields or calculation logic change, a cited authority changes its guidance, a new product category is introduced, or the regular review date arrives. New regulated products can require a different workflow rather than another checkbox. Preserve template versions so a team can identify which rules generated an earlier result.
Production readiness also precedes delivery-route selection. Once the exact goods and market are accepted, the international gift-shipping comparison can help organize the separate carrier, customs and payer questions. A carrier quote should refer to the accepted product, not become an indirect approval of an unspecified substitute.
Download the editable request workbook
Download the English request and change-control workbook (XLSX, v1)
Use one copy per SKU and target market. Replace the worked-example inputs, preserve accepted versions, and test the hold conditions before sending a live request.
Bring the accepted product brief to Giftpack
Giftpack supports custom merchandise development, sampling, production and global delivery, with branded storefront and gifting workflows for suitable programs. Bring the accepted product definition, proof version, intended markets and delivery needs into that conversation. They give the project team a clearer starting point than an isolated image and a requested arrival date.
Ask which parts of sourcing, sampling, fulfillment and recurring ordering fit your actual scope, and agree who owns each outstanding product or market decision. Keep the workbook's approval history with the project. It helps everyone explain why the current version can proceed and what must reopen if the product changes again.