Add Minimum Order Value to the Offer Card Before Producing Creative

01

1. Classify the restriction before creating the offer card

A minimum order value is a basket-level spend requirement. It is not automatically the same as a minimum quantity or the amount required to receive free shipping.

Google supports minimum order values through account-level shipping settings and the product-level minimum_order_value attribute. According to Google, the attribute should be used when a merchant does not ship a product below a specified order value. A product-level value overrides an account-level minimum for that offer.

A minimum order quantity is different. If shoppers must purchase five units, the restriction concerns the number of units rather than the total basket value. Google instructs merchants selling products in bulk or subject to a minimum quantity to submit the price for the minimum purchasable quantity. If five units at $8 each are required, the submitted product price should represent the $40 minimum purchase—not an $8 single-unit price.

A free-shipping threshold is also different. If a shopper can place a $20 order but must pay shipping until the basket reaches $50, the store does not have a $50 minimum order value. Google specifically says not to set a minimum order value when orders below the threshold are still allowed and merely incur a shipping charge.

This classification controls the wording. Use “$30 minimum order” for a mandatory basket value, “minimum quantity: 5 units” for a unit requirement, and “free standard shipping on orders over $50” for a shipping promotion. Mixing these terms can cause the ad, landing page, feed, and actual checkout experience to describe different offers.

1. Attempt to place an order below the threshold in the target market.
2. Record whether checkout blocks the order, requires more units, or simply adds shipping.
3. Classify the rule as minimum order value, minimum quantity, or free-shipping threshold.
4. Do not approve creative until the commercial owner and feed owner agree on the classification.

02

2. Build one offer-control card for each applicable rule

The offer-control card should be the approved source used by media buyers, creators, landing-page editors, localization reviewers, and feed operators.

Start with a stable offer ID and a plain-language restriction type. Record the destination market, currency, shipping service, sales surface, exact amount, affected products, and what checkout does when the requirement is not met. Add approved short and long wording, prohibited wording, implementation location, owner, approver, effective date, and retirement date.

Google’s product-level attribute requires country and price sub-attributes. It also supports optional service and surface values. Google permits the field to be repeated for different applicable records, which makes it possible to describe different requirements by market or shipping service. The minimum-order currency must match the submitted product-price currency.

Do not put “US and Canada: $30 minimum” on one card if the Canadian checkout uses CAD or a different local amount. Create separate records. The same rule applies when standard and express delivery have different requirements. Shopify Markets can support market-specific configurations involving currency, pricing, content, product availability, and shipping options, so the production record should identify the exact storefront context being reviewed.

A useful evidence field prevents approvals from becoming a matter of memory. Attach a dated screenshot of the product page and cart, a test-checkout record, the relevant feed export, and the final approved copy. Evidence should show the market, currency, service, and date rather than only the threshold amount.

1. Record: offer ID, restriction type, market, country code, currency, shipping service, surface, amount, and product scope.
2. Describe the below-threshold checkout behavior in one sentence.
3. Add short ad wording, explanatory landing-page wording, quantity wording if relevant, and prohibited phrases.
4. Name the commercial approver, feed owner, creative owner, and localization reviewer.
5. Set effective, review, and retirement dates.
6. Attach dated website and feed evidence before changing the status from draft to approved.

03

3. Lock approved minimum-spend wording

Creators should copy controlled wording from the offer card rather than paraphrasing the restriction independently.

Create reusable tokens for each context. A short overlay can use “Minimum order: {{MOV}}.” A sentence can use “A minimum order of {{MOV}} applies.” If the rule depends on delivery service, use “{{SERVICE}} orders require a minimum spend of {{MOV}}.” Cart messaging can say, “Add {{REMAINING_AMOUNT}} to meet the {{MOV}} order minimum.”

Keep quantity and shipping language in separate token families. Use “Minimum quantity: {{QUANTITY}} units” for a unit requirement. Use “Free {{SERVICE}} shipping on orders over {{THRESHOLD}}” when smaller orders remain possible. These are not stylistic alternatives to minimum-spend wording; they describe different checkout outcomes.

Prohibit ambiguous shortcuts. “Starting at $10” can mislead when the shopper must build a $40 basket. “Buy more and save” does not disclose a mandatory minimum. “$50 shipping minimum” does not explain whether $50 is required to order or merely required to avoid a shipping fee. An amount without its market or currency can also be unsafe when creative is reused internationally.

Google determines whether the Merchant Center minimum-order annotation appears based on factors that include product price and the cheapest available shipping service. Do not assume that a feed annotation will appear on every impression or repair ambiguous wording in a paid-social asset. The ad and destination should make the applicable condition understandable on their own.

1. Approve one short label, one full sentence, one cart instruction, and any service-specific version.
2. List phrases creators must not use.
3. Include the market and currency in asset names or production metadata.
4. Require a new approval when the amount, service, market, or checkout behavior changes.

04

4. Route the card into briefs, ads, landing pages, and localization

Every production brief should point to the same offer ID and reproduce its approved terms without modification.

Add a mandatory offer-controls block to the brief containing the offer ID, target market, shipping service, approved disclosure, required placement, prohibited wording, landing-page URL, and review date. The creator should not need to open Merchant Center, interpret a supplier message, or ask which threshold is current.

Review every place where the offer can be stated or implied: headlines, primary text, image overlays, comparison graphics, video hooks, title cards, voiceovers, subtitles, captions, creator talking points, calls to action, and end cards. A correct caption does not fix an incorrect spoken amount, and a correct end card does not fix a hook that describes free shipping as a mandatory order minimum.

On the website, show the condition early enough for a shopper to understand it before trying to complete the purchase. Repeat it where useful in the cart, shipping information, or policy page. Google requires submitted minimum order values to match the website. Its price guidance also requires submitted product pricing to agree with the landing page and checkout context.

For multilingual stores, treat each translation as a controlled variant rather than replacing the currency symbol mechanically. Shopify’s Translate & Adapt documentation says merchants can adapt content for markets and use different media by language; it also recommends reviewing automatic translations before publication. Your review should confirm meaning, amount, currency, shipping-service name, and local formatting.

1. Insert the offer-control block into the creative brief.
2. Link each asset and localization to the applicable offer ID.
3. Compare every written and spoken claim with the approved token.
4. Open the destination page in the intended market and language.
5. Verify that the product page, cart, policy copy, and checkout describe and enforce the same rule.
6. Retire old assets when a threshold changes rather than silently editing only the feed.

05

5. Implement and inspect the Merchant Center field

Feed QA should verify the attribute structure, applicable products, currency, service names, and interaction with shipping settings.

A simple text-feed value can be structured as US:30 USD under a minimum_order_value header. A service-specific structured header can use minimum_order_value(country:service:surface:price), followed by values such as US:standard:online:30 USD,US:express:online:50 USD. Follow Google’s current attribute specification for the feed method you use.

The structured header and each submitted value need the same sub-attributes in the same order. An incomplete or mismatched structure can trigger an invalid-format issue. Service names should correspond to the services used in the related shipping data, and the minimum-order currency must match the product-price currency.

Google says to submit the product-level attribute when the product price is equal to or below the minimum required order value. The product-level setting overrides the account-level value, so exceptions must be deliberate. If restrictions apply only to a defined product group, document that scope on the card instead of assuming every offer inherits the same rule.

Dropshippers should pay particular attention to shipping data supplied by feed applications or product-level rules. Google says offer-level shipping or carrier_shipping data can override account-level shipping settings, including an account-level minimum order value. When an offer-level shipping attribute is used and a minimum still applies, the product-level minimum_order_value must also be submitted.

1. Confirm that every affected offer has the intended minimum-order record.
2. Verify country, currency, surface, and service values.
3. Check whether product-level shipping is being supplied by an app or feed rule.
4. Confirm that a required product-level minimum was not lost when shipping data overrode account settings.
5. Review Merchant Center’s diagnostics or “Needs attention” area.
6. Compare the final processed feed with the live website—not only with the source spreadsheet.

06

6. Run the pre-launch creative and commerce QA checklist

The final review should test the rule as a shopper experiences it, then trace the same facts back through the feed and creative package.

Offer control: confirm that the order rule is active, correctly classified, approved by market and service, and documented for product or supplier exceptions. Verify the effective date and identify who can pause or replace the rule.

Website: inspect the product detail page, cart, shipping information, and checkout on mobile and desktop. Change the destination market where applicable. Confirm that the amount, currency, terminology, and service remain consistent and that the actual below-threshold behavior matches the disclosure.

Feed: verify the minimum_order_value record, country code, price currency, service mapping, applicable product scope, and any product-level override. For minimum-quantity products, confirm that the submitted price represents the minimum purchasable quantity. Review current Merchant Center diagnostics before launch.

Creative: check every static, video, caption, script, voiceover, end card, and localized export. Confirm that no asset confuses minimum spend with quantity or free shipping. Search the asset library and active production queue for the previous amount. A perfect new campaign can still conflict with an older evergreen ad.

After completing these offer-specific checks, use a broader ecommerce launch review to catch destination URLs, tracking, legal copy, rendering, and version-control issues that are outside the minimum-order rule itself.

1. Place a below-threshold test order for each relevant market and shipping service.
2. Capture the observed product page, cart, and checkout behavior.
3. Inspect the processed feed record and Merchant Center diagnostics.
4. Read all creative text and spoken copy against the approved card.
5. Review localized assets manually.
6. Confirm that outdated assets and briefs have been retired.
7. Record the approval, evidence, and remaining exceptions before launch.

07

7. Preserve the decision and subsequent learnings

A minimum-spend rule should have one controlled source, not separate versions maintained in a feed sheet, brief, ad account, and landing-page document.

At minimum, keep the approved offer card beside the brief, source assets, localized variants, feed-QA evidence, launch date, and change history. When the threshold changes, create a versioned update that identifies which assets, pages, and feeds require replacement. Do not overwrite the old amount without preserving when and where it was used.

ATIYO can organize the roadmap item, offer context, brief, assets, iterations, approvals, and reusable observations in one creative-strategy workflow. It does not connect to ad accounts, buy media, calculate ROAS, or automatically know performance. Media performance remains in the ad platform, while ATIYO preserves creative context and learnings that a user chooses to record.

That distinction matters operationally. A feed diagnostic belongs in Merchant Center, checkout behavior belongs in the commerce platform, and campaign results belong in the ad platform. The creative operating record should connect those external facts to the offer version and asset decisions without pretending to replace their source systems.

If you want to manage the offer card, brief, versions, and review evidence together, start ATIYO’s card-confirmed seven-day trial. Billing begins afterward on the selected plan.

1. Create a versioned record for the approved minimum-spend rule.
2. Attach the brief, landing-page reference, feed evidence, and final assets.
3. Record revisions instead of overwriting the prior threshold.
4. Enter relevant performance observations manually while retaining the ad platform as the source of media results.