A global gift catalog is not a promise that every item can be offered in every market. A country-and-category eligibility register turns that uncertainty into a controlled decision: which market, category, and item can be shown; which evidence supports the decision; when it expires; who owns it; and what approved substitute appears when the preferred choice cannot proceed.
Start with the decision the register must control
The useful question is not “Do we ship to Japan?” or “Is food allowed in Taiwan?” Those questions are too broad. A defensible decision names a market, a category, a specific stock-keeping unit, an intended route, a business program, and an effective period. It also separates four different facts that teams often compress into one green check mark.
First, catalog availability asks whether an item is currently offered, stocked, or sourceable for the market. Second, delivery eligibility asks whether the chosen carrier and service can accept the item and route it to the destination. Third, company eligibility asks whether the employer or program permits that gift for the recipient and occasion. Fourth, local review asks whether the applicable customs, product, tax, employment, privacy, or other specialist has approved the conclusion the business needs. None of these facts proves the others.
Postal guidance illustrates why the separation matters. The United States Postal Service says that almost all dangerous materials are prohibited in international mail and that destination-country limits can further restrict the few exceptions. Chunghwa Post publishes prohibited and dangerous-item guidance for Taiwan. Japan Post warns that destination-specific restrictions can lead to rejection or return after acceptance. Korea Post provides country-specific conditions and prohibited-item information. These sources are route evidence, not a universal catalog ruling, and they can change.
Define the controlled object as market + category + stock-keeping unit (SKU) + route + program + effective period. If any element changes, the decision is a new decision or needs revalidation. A “global” item can therefore be Approved in one market, Pending in a second, and Blocked in a third without contradiction.
Download the localized eligibility-register workbook
Use the workbook that matches the operating team’s language. Each file contains seven localized worksheets: Instructions, Markets, Categories, Rules, Assortment, Substitutions, and Validation. Formula cells calculate a final decision, identify overdue reviews, require a substitute when a choice is not approved, and summarize unresolved controls. The sample rows are explicitly illustrative and must be replaced before release.
-
Version: 4.0, verified October 21, 2026
-
Method: join Market ID, Category ID, and SKU ID; evaluate availability, delivery, company, and local-review evidence; then apply the approved fallback rule
-
Refresh cadence: quarterly and after any material regulation, carrier, catalog, supplier, product, or program change
The workbook is an operating template, not a legal opinion, customs determination, carrier acceptance, tax conclusion, or statement of Giftpack catalog coverage. Keep a copy of the source URL, its effective or verification date, the owner who interpreted it, and the next review date. When evidence is missing or expired, mark the row Pending and suppress the choice rather than treating silence as approval.
Build stable identifiers before collecting decisions
Names are poor keys. “Japan,” “JP,” and “日本” can refer to the same market, while “gift card,” “digital reward,” and a vendor’s product name can hide different issuance and redemption rules. Stable identifiers let the team change display language without breaking history.
Create one Market ID for each operating market, not merely each country. A market may differ by legal entity, fulfillment route, currency, or service promise. Create a Category ID for the decision boundary that owners can actually govern. “Food” may be too broad if shelf-stable snacks, alcohol, fresh produce, supplements, and chilled goods follow different evidence paths. Create a SKU ID for the item or controlled variant. Size, material, battery configuration, bundle contents, or personalization method may require separate rows.
Use a rule ID to connect the market and category decision, and a substitute ID to identify the approved fallback. Do not make the substitute a free-text note. A structured substitute has its own market, category, SKU, approval status, effective date, owner, and evidence. Otherwise the primary item can be blocked correctly while an unreviewed replacement slips through.
The minimum row also needs a source URL, source owner, verification date, effective date when known, next review date, decision status, reason, and change record. The owner is a person or accountable function, not “operations.” When ownership changes, update the register and preserve the prior record.
| Field | Purpose | Acceptance test |
|---|---|---|
| Market ID | Defines the operating market and route context | One unambiguous owner and currency or operating profile |
| Category ID | Groups items that share a review path | Narrow enough that one decision rule is meaningful |
| Decision status | Approved, Pending, or Blocked | Supported by dated evidence and an accountable approver |
| Next review | Prevents a stale approval from living forever | Date is present, monitored, and earlier changes trigger review |
| Substitute ID | Provides a reviewed fallback | Replacement is independently approved for the same market |
Use three statuses and make uncertainty visible
Three statuses are enough when their meanings are strict. Approved means every required control for the stated scope is supported, current, and owned. Pending means the team lacks evidence, an approval, a current date, or a tested route. Blocked means a known rule, business decision, carrier limit, product condition, or risk decision prevents the offer.
Pending is not a softer Approved. The customer-facing catalog must not expose a Pending item. It is a work queue with a named owner, missing evidence, next action, and due date. Blocked is not necessarily permanent. Record the reason and the event that could reopen review, such as a new locally sourced variant or an approved nonphysical reward.
Calculate the final decision conservatively. If any required control is Blocked, the row is Blocked. If all required controls are Approved, the row is Approved. Every other combination is Pending. The logic prevents a broad catalog flag from overriding a specific shipping or policy problem.
IF any required control = Blocked → Blocked
ELSE IF every required control = Approved → Approved
ELSE → Pending
Keep “not applicable” distinct from blank. A blank cell means nobody has supplied the answer. Not applicable means the owner considered the control and documented why it does not govern this row. The workbook validation sheet should count missing evidence, overdue reviews, Pending or Blocked rows, and items that need an approved substitute. Zero errors does not prove every business conclusion is correct; it proves the register is internally complete enough for accountable review.
Assign owners by decision, not by spreadsheet tab
Global merchandise operations owns the register’s structure, release rule, version, and change process. Regional procurement or market operations owns local supply and substitution evidence. Fulfillment owns route testing, carrier constraints, packaging conditions, and service-level evidence. Program owners define recipient eligibility, occasion, value band, and company policy. Qualified legal, tax, customs, employment, privacy, or other specialists own conclusions that require their expertise.
One person can hold several roles in a small program, but the decision rights should remain separate. A carrier can describe its acceptance conditions but cannot approve the employer’s gifting policy. A platform can execute a configured catalog but cannot decide whether a gift is taxable, legally permissible, or culturally suitable. A procurement manager can confirm an item is sourceable but cannot infer that a postal route accepts it.
The register should also show who can change each field. Limit status changes to named owners. Require a reason when Approved becomes Pending or Blocked, and when a Blocked row reopens. Protect formula columns, preserve the prior version, and record the release cutoff used by each campaign.
A simple operating rhythm works well: market owners update evidence; operations runs validation; specialist owners resolve exceptions; the program owner approves the release snapshot; and fulfillment tests representative routes. The release snapshot is immutable evidence for that campaign. Later changes create a new version rather than rewriting what recipients previously saw.
The global corporate gifting operations hub explains how this register fits into policy, funding, recipient experience, delivery, reconciliation, and measurement. The localization guide expands the language, currency, catalog, cultural, and quality controls that a simple country flag cannot represent.
Execute the register in seven controlled steps
1. Define the release scope. Name the program, recipients, markets, reward forms, budget band, fulfillment routes, and release date. State what the register does not decide. If the campaign includes employee, customer, and partner audiences, decide whether their policy paths require separate rule sets.
2. Load markets and categories. Add only markets the business intends to support. Break broad categories where evidence differs. Record currencies, locale, market owner, category owner, and default review cadence.
3. Collect primary evidence. Prefer official carrier, postal, regulator, supplier, and product sources. Read the underlying page or document, not a search snippet. Record the relevant section, geography, route, verification date, and limitation. If a source describes only its own service, do not generalize it to every route.
4. Build rule rows. Combine market and category, assign Approved, Pending, or Blocked, and name the approver. A rule row may be Pending while research continues. Do not postpone recording it until the answer is favorable.
5. Join the assortment. Map each SKU to its market, category, route, and rule. Confirm current sourceability and the exact variant. Let formulas calculate the final decision and review flag; do not type over formula results.
6. Add approved substitutes. For every commercially important Pending or Blocked primary choice, evaluate a substitute through the same controls. A substitute may be a different item, locally sourced category, nonphysical reward, or no-offer outcome. “No substitute” is a valid documented decision.
7. Validate and release. Resolve missing owners, sources, dates, and substitute actions. Test representative rows at the boundaries: one fully Approved item, one known Blocked item, one expired source, one missing review date, and one primary item with an approved replacement. Export or freeze the campaign snapshot and retain its hash or version identifier.
Hypothetical case A: one food hamper across three markets
Assume an illustrative employee-recognition campaign wants to offer the same shelf-stable food hamper in the United States, Taiwan, and Japan. This is not a customer result and does not state that the hamper is available through Giftpack.
The global program owner defines the occasion, budget, recipient population, and acceptable alternative. Procurement creates one category for shelf-stable packaged food and a separate category for any alcohol or supplement component, because their evidence paths differ. The SKU record lists every included item and the exact package configuration.
For the United States row, fulfillment verifies the intended origin and route using current USPS or carrier guidance, while a local owner checks the item and program requirements. For Taiwan, the owner reads current Chunghwa Post and applicable import or ingredient evidence for the actual contents and route. For Japan, the owner checks current Japan Post conditions and any item-specific entry requirements. The team does not copy an Approved result from one market to another.
Suppose supply is confirmed in all three markets, but Taiwan ingredient evidence and Japan import evidence remain incomplete. The register shows US as Approved only if every required control is satisfied; TW and JP remain Pending. The catalog suppresses the hamper in those markets. It does not show the item with a warning and ask the recipient to discover the failure later.
The substitute table contains a locally sourced nonfood merchandise kit for Taiwan and a digital reward for Japan. Each alternative has its own approval row. If the Taiwan substitute is Approved but the Japan digital reward still lacks currency or recipient-eligibility evidence, the Taiwan experience can proceed and Japan remains Pending. Recovery is precise: the TW owner verifies the replacement source and activates the mapped substitute; the JP owner completes the reward review or selects another approved path.
Acceptance evidence includes the three final rows, source dates, owner approvals, successful sample-route checks where appropriate, the catalog snapshot, and proof that no Pending SKU appeared. The failure lesson is equally important: “available globally” never replaced item-level evidence.
Hypothetical case B: a digital reward works in two of three markets
Assume a client-appreciation program proposes one digital reward for the United States, Japan, and Korea. Again, the scenario is illustrative. A digital reward avoids physical shipping, but it still requires review of issuance market, currency, redemption conditions, recipient eligibility, expiry, refund handling, company policy, and support.
The program owner creates a digital-reward category, while procurement records the exact product and issuer. Finance owns currency and funding treatment. Regional owners confirm that the reward can be issued and used by the intended recipient population. Support documents what happens when delivery succeeds but redemption fails.
Suppose the reward is approved for the United States and Japan but unavailable in Korea. The final decision is Approved for US and JP and Blocked for KR. The Korea row links an Approved non-digital merchandise alternative sourced for the local market. The recipient sees one valid choice; they never see the unavailable digital option.
Now suppose the issuer changes its redemption territory. The source owner records the material change, moves affected rows from Approved to Pending, and triggers review before the next campaign. Operations identifies campaigns using the old register version, pauses unreleased catalogs, and asks support to watch any already issued rewards. After verification, the rows return to Approved or map to a substitute. The change history preserves both the old decision and the new effective date.
Acceptance evidence includes issuer documentation, market and currency mapping, company approval, support instructions, test redemption where authorized, and a catalog check for each market. A successful email delivery is not the acceptance test; the recipient must be able to use the reward under the promised conditions, or receive the approved fallback.
Connect the register to catalog, recipient, and support controls
The register should publish decisions to a catalog configuration, not become a second catalog. Keep one source of truth for the status and effective version, then pass only Approved market-item pairs to the presentation layer. Preserve the register version with the campaign so support can reconstruct what the recipient was offered.
Recipient data should not be used as an informal policy engine. Determine market from an approved profile or a recipient-confirmed destination at the appropriate stage. Collect only what the program needs, and do not expose specialist notes in the recipient experience. The recipient-data operations hub provides a broader lifecycle for eligibility, invitation, address, support, retention, and deletion evidence.
Support needs three answers: the status shown at release, the evidence and owner behind it, and the approved recovery route. If an order fails because a condition changed after release, classify the incident separately from a setup error. Move affected rows to Pending, contain new offers, identify open orders, and apply the approved substitute or refund path. Do not silently edit a row and leave active campaigns on an unknown version.
Measure control quality, not just order volume. Useful measures include the share of active rows with current evidence, number of overdue reviews, percentage of blocked primary choices with approved substitutes, time to resolve a Pending row, and number of recipient-facing failures caused by stale eligibility. Keep any outcome claim Unknown until the organization has a reliable measurement source.
Review changes, failures, and evidence as one operating cycle
Quarterly review is the floor, not the only trigger. Revalidate after a postal or carrier update, supplier or catalog change, product reformulation, route change, new legal entity, new reward issuer, currency change, incident, recipient complaint, or specialist instruction. Store the source-verification cutoff separately from the campaign release date.
Use a bounded recovery path. A missing or expired source produces Pending, suppresses the item, assigns an owner, and creates a dated next action. A known prohibition produces Blocked and an explicit reopening condition. A workbook or formula defect is corrected and retested. A disputed specialist conclusion goes to the responsible human owner; operations does not relabel it Approved to meet a deadline.
Test both success and failure. Confirm that an Approved row can reach the intended catalog. Confirm that a Blocked row cannot. Delete a source date and verify that the validation summary finds it. Expire a review date and verify the review flag. Remove an approved substitute and verify that the workbook requests action. Restore the inputs and retain the test results with the release version.
The register is complete only when each released choice can be explained in one sentence: “This SKU was offered to this market for this program under register version X because supply, delivery, company, and local-review evidence were current; owner Y approved it; substitute Z was available; and the next review date was D.” If the team cannot produce that sentence, the item is not ready.
Make the register a release gate, not a shelf document
A country-and-category eligibility register creates value when it changes what recipients can actually choose. Stable identifiers prevent translation and naming drift. Separate controls prevent catalog availability from masquerading as legal or delivery approval. Strict statuses make uncertainty visible. Dated evidence and approved substitutes turn research into a repeatable recovery path.
Start with one real program and a small set of representative markets and categories. Populate primary sources, name owners, run the boundary tests, and release only the Approved snapshot. Expand after the team can explain every choice and every fallback. The goal is not a permanently green spreadsheet; it is a trustworthy decision system that pauses safely when facts change.
Once the company has made and approved those policy, market, category, and specialist decisions, Giftpack can serve as an execution layer for configured recipient choice and global fulfillment. Giftpack does not replace legal, tax, customs, postal, privacy, payroll, employer, or local-market judgment; exact catalog and country support should be confirmed for the program before launch.