- The old Available to Try signal depended on floor-sample reason codes, so it went empty whenever tagging slipped.
- The fix treats positive quantity at a location as the signal, and a kit only counts when every component clears that location.
- Incomplete component data fails closed so the badge never overpromises.
- Strict versus loose reason-code rules is a real tradeoff that depends on how reliably floor samples are tagged.
Shoppers trust a simple promise: “Available to try” at a store near them. When that badge is wrong—especially on furniture and appliance kits—you burn a trip, a floor conversation, and a little of the brand’s credibility.
At a furniture retailer, that badge is not a marketing toggle. Middleware reads live STORIS inventory, writes location IDs onto Shopify variant metafields, and the theme turns those IDs into store names shoppers recognize. The hard part is kits: a sofa set, a bedroom group, anything sold as one SKU but built from several component SKUs in the warehouse.
What broke the old signal
The earlier rule leaned on floor-sample (“as-is”) reason codes. If purchasing stopped tagging floor samples that way—or STORIS stopped returning them consistently—the metafield went empty. No locations meant no “Available to try,” even when sellable stock sat on the floor.
The fix is blunt and better: treat positive quantity at a location as the signal. Ignore floor-sample reason codes for this badge. If a location has usable inventory, it can appear. If quantity is zero or missing, it cannot.
Kits need intersection, not optimism
A single SKU is easy: scan each location’s available quantity and keep the ones above zero.
A kit is different. Showing a kit as tryable at Store 012 only works if every required component has enough stock at Store 012 for the kit quantity. One missing nightstand should not let the whole bedroom kit light up green.
So the middleware now builds, per location, a checklist of kit component SKUs. A location passes only when every component clears that checklist. Incomplete component data fails closed: if we cannot load a component’s inventory JSON, that location stays off the list rather than guessing.
Why fail closed matters for furniture ecommerce
False positives are expensive in showroom retail. A customer drives across town for a kit the store cannot demo. The associate scrambles. Online trust drops a notch.
False negatives hurt too—but they are recoverable with a call or another store. Inventory integrations should bias toward honesty when data is incomplete. That is the same discipline behind good Shopify + STORIS sync and answer-engine-ready catalog truth: publish what you can prove.
What we tried, what broke, and the tradeoff
The reason-code rule has gone back and forth across the furniture projects we support. On one, we first synced only floor-sample (FS) as-is reason codes to the badge. In September 2025 the client asked us to drop that filter so every as-is product we could see would sync. In April 2026 store staff said items they could see as as-is at two locations were missing from the site. We queried the ERP directly and those SKUs were not in its payloads either, and the middleware had no filter that explained it. It only remapped one location code to another. The next step was a ticket with the ERP vendor, and we restricted one location back to floor-sample codes only while that was sorted out.
The tradeoff is real. A loose rule shows more stock but can surface items that were never meant to be demoed. A strict rule is safer but empties the badge whenever tagging slips. On the project in this post we chose positive quantity at the location, with the kit checklist above as the guard, and we accept that it depends on clean quantity data. Your answer depends on how reliably your team tags floor samples.
What the storefront needs
Middleware writes available_to_try_at_location_ids. The theme still has to map those IDs to location metaobjects shoppers can read. When STORIS finally returns the full location list in product detail, those IDs become real store names instead of silent gaps.
If you run kits on Shopify with an ERP behind the curtain, ask one question of your “Available to try” logic: does a kit light up only when every piece is actually there? If not, shoppers will teach you the answer the hard way.
Curious how we wire inventory truth into commerce for furniture brands? See our furniture ecommerce solutions, our Shopify and STORIS work, the STORIS-to-Shopify migration case study, or start with ecommerce development.