
A shopper in Christchurch finds a kettle on Google, sees it available nearby and drives to the branch. The only unit is a display model the store cannot sell. The stock count was technically correct, but the listing made a promise the branch could not keep.
For New Zealand retailers with physical stores, Google local inventory can help shoppers find products nearby. The investment decision is whether to publish branch availability now, start with a smaller group of products and stores, or first improve the stock and pickup process. The feed is only one part of that decision. The product page and branch need to tell the same story.
This guide covers the handoff between stock records, Google Merchant Center and the store. It is aimed at retail leaders planning an implementation or deciding whether a feed that already exists is reliable enough to expand.
Key Takeaways
- Choose the availability or pickup promise each branch can meet.
- Match product variants and branch codes across the feed and landing page.
- Test last units, stale stock and collection cutoffs before expanding.
Decide what the shopper can actually do
Begin with a shopper who wants a particular variant at a particular branch. Decide whether your business can show where the item is available, let that shopper reserve or order it for collection, or arrange for the product to reach the branch later. Each option needs different data and store procedures.
Google’s local inventory overview includes New Zealand among supported countries. Free local listings and local inventory ads are separate surfaces. An eligible local listing can support product discovery, while an ad adds paid distribution. Confirm which experience your account and site can support before committing to a campaign.
The ability to display availability should be assessed separately from pickup. An item may be available to a walk-in shopper without your store offering an online reservation. Conversely, a branch may accept pickup orders for products transferred from elsewhere. Decide what the landing page will say and which actions the shopper can complete from it.
Use existing customer questions to choose your first use case. A retailer that regularly answers calls about branch stock might start by showing reliable availability. A chain with a proven collection process might prioritise online pickup. OSE’s click and collect guide covers the wider customer and store process.
Choose the first stores and products deliberately
Pick locations that can maintain reliable inventory and have someone accountable for exceptions. A small pilot with different trading patterns can be more informative than a broad launch where store teams have inconsistent procedures. Ask each branch how it treats display stock, transfers, returns and customer holds.
Choose products where customers benefit from knowing whether a particular variant is nearby. A boxed appliance with a stable stock record can be a manageable first case. A product that staff sell in multiple units of measure, or an item with frequent stock discrepancies, may need more data work before inclusion.
Consider an illustrative NZ chain with one Christchurch branch and one regional branch. Both sell the same appliances, but the regional store receives transfers on a different schedule. Start by testing ordinary branch stock in both locations. Test transfer-based collection separately so it does not inherit the promise for an item already on the shelf.
Give the pilot a boundary in writing. Record participating branches, products, the intended customer action and the stock conditions that should exclude an item. Specify who can remove an unreliable store or product from the pilot. This helps teams contain an issue while leaving dependable listings available.
Establish what “available” means at each branch

A physical count may include products already allocated to pickup, damaged boxes, display units and stock awaiting inspection. Agree which quantities can be offered to a new shopper. Ask the stock owner to show which of those states the ERP, POS or inventory service can distinguish today.
Set rules for low quantities and stale data. A branch that reliably counts individual products may be comfortable showing the last unit. Where counts or reservations lag, it may be safer to withhold that promise until the records improve. Measure how often that choice suppresses an item that could have been sold and how often it prevents an inaccurate listing.
Plan for the last-unit race. A customer in the aisle and a customer placing a collection order can want the same item. Define what commits it, when the commitment is released and what staff do if they cannot find it. The availability feed can help someone decide to visit. A reservation or confirmation requires an operational event that the store can support.
Trace sales, cancellations, returns and transfers through the stock record. Measure the delay between the branch event and the resulting website and feed updates. Use the busiest period you can reproduce during testing. Our inventory accuracy guide explains how to assign responsibilities across stores, warehouses and the ERP.
Connect the product, branch and availability records
Google’s local inventory data specification describes the attributes for matching a product and store, including the product identifier, store code and availability. Build a mapping between the identifiers in the product data, stock system and Business Profile locations. Use stable identifiers that can survive a branch rename or a change in merchandising text.
Check variants individually. A product family can have one colour in stock while the advertised variant is unavailable. Confirm the item identifier and selected variant after a customer follows the listing. When a branch stops carrying an item, test how the feed and page represent the change. A missing row and an explicit unavailable state should be handled according to the selected integration’s documented behaviour.
Decide what to do when the feed runs but some data is stale. A successful job can still publish an old stock count. Monitor the age of the underlying records by branch, as well as feed errors and match failures. Establish when a stale location should be withheld and how the team can restore it after confirming fresh data.
Keep prices aligned wherever your chosen experience requires them. Confirm the price presented for the NZ store and variant, including any local price differences. Where a product has a separate trade price behind sign-in, verify which price can legitimately be shown to the public. Test logged out and with no remembered store selection.
Test the page a shopper reaches from Google

For the store-specific page experience, Google’s landing-page guidance describes a store parameter in the product URL that matches the Business Profile store code. Confirm the requirements for your selected setup. The shopper should be able to recognise the branch, variant and availability represented by the listing.
Open a test link in a fresh mobile session. Check that a location remembered from an earlier visit cannot override the location in the URL. Try an unknown store code, a product no longer sold at that branch and a variant with a different availability state. Give shoppers clear alternatives when the original option is unavailable.
If the same storefront serves both New Zealand and Australia, test the NZ link with a new session from the relevant market. Verify that it preserves the New Zealand store and price context through any redirect or country selector. The handoff should survive a shared link, a logged-out visit and an ordinary checkout attempt where pickup is offered.
Test the whole journey with staff. A page can correctly show the local product while the checkout changes the chosen store or offers an unavailable service. Compare the branch displayed to the customer, the branch on the order and the branch that receives the pick request. This is a useful acceptance test for a theme, plugin or integration proposal.
Offer pickup timing that branches can meet

Google’s pickup today guidance specifies same-day or next-day pickup for items opted into that feature and lists New Zealand support for free local listings. Validate the relevant programme and landing-page requirements before enabling it. Give the branch a measurable collection promise it can support.
Document the local cutoff, trading hours, preparation time and what happens on a public holiday or during a temporary closure. Test a late Friday order and a closure day. A merchant’s website and store team need a shared understanding of when an order will be ready and when the customer should travel.
Keep the ready-for-collection notification tied to actual preparation. An order confirmation can acknowledge the purchase without telling the buyer to leave immediately. If a branch cannot locate the item, route the exception to someone who can contact the customer and offer an approved next step.
Where stock is transferred into a store for collection, establish a separate promise and verify the selected Google setup. The presence of stock at a distribution centre does not make it available for immediate collection at the branch. Check the transfer and receipt events before offering a ready time.
Use the pilot to decide whether to expand
Test at least one normal listing, one low-stock item, one variant mismatch, one stale branch and one cancelled collection. For each case, write the expected result in the inventory system, Merchant Center, product page and store. Include who receives an alert and what they should do before the next shopper relies on the listing.
Review feed errors and website mismatches alongside customer outcomes. Track how often shoppers see an item that the branch cannot provide, how often pickup is ready when promised and which exceptions require staff contact. Define each measure before launch so the pilot can be compared with later releases.
Use Merchant Center and any relevant advertising reporting for visibility. Use website and order data for collection activity and cancellations. Keep the interpretation conservative. Listing interactions may indicate interest in a branch, but a visit or sale requires separate evidence. If running paid activity, agree what conversion data is available before judging spend.
A pilot can justify a feed connection, better POS or ERP integration, or a small set of operational changes. Choose the next investment from the failures you can demonstrate. For a discovery discussion with OSE, bring your NZ store codes, a sample product and inventory export, two representative landing pages and pickup exception examples. That gives the team enough context to scope a test across the feed, product page and store. Discuss your local inventory project with OSE.
Frequently asked questions
Google lists New Zealand among supported markets. Confirm the programme and product page experience available for your account. Start with a representative branch and variant, then check that the listing, page and store show the same availability.
Google provides free local listings and paid local inventory ads. Check the eligibility and onboarding requirements for the experience you want. A pilot can focus on inventory and page accuracy before you decide whether paid distribution is justified.
Only offer availability that reflects what the shopper can obtain at that branch under the chosen experience. A transfer from a warehouse can support a later collection promise when the operational process and programme requirements are met.
Use the reservation or allocation state when deciding what stock to show to a new shopper. Test how a sale, cancellation or expired hold changes availability. Agree how staff handle a mismatch before you advertise low quantities widely.
Follow one variant from a branch stock event to the Google listing and landing page, then place a pickup order if offered. Check the selected store, price, readiness message and pick instruction. Repeat with a stale or unavailable item to test recovery.