Skip to main content

Understanding Location & Region Overrides

How location and region overrides work now that creating one is an explicit, opt-in choice instead of the default, and who can create them.

Written by Gildas Burnel

What's a location or region override?

By default, edits you make to an item or category apply to your whole shared catalog — every location. An override lets you set a different value (price, availability, hours, and so on) for just one location or one region, without changing it everywhere else.

Edits apply to all locations by default

When you edit an item in your shared catalog, your change applies to all locations unless you explicitly choose otherwise. Creating a location- or region-specific override is a deliberate, separate choice — Stream will never silently create one for you.

Creating an override

To scope a change to a single location or region instead of your whole catalog, choose that location or region from the scope selector before saving. Stream shows a confirmation naming exactly which layer — location or region — you're about to create an override for, so you can confirm that's what you intended before saving.

Who can create overrides

Administrators can grant or restrict the ability to create location and region overrides on a per-role basis, using the Create Location/Region Overrides permission. If a team member's role doesn't have this permission, their edits will always apply to all locations — they won't be able to scope a change to a single location or region.

Related Articles

Did this answer your question?