Skip to content
WooCommerce Solutions · Regional Catalogs & Shipping
Location-Based Product Availability
Where a customer is changes what they can buy: different carriers, different services, different restrictions. We build the visibility, restriction and carrier logic that lets one WooCommerce catalog serve several markets correctly.
Official DHL plugin
Built and maintained by us, free on WordPress.org
Fixed quote, written scope
You know what’s included and what it costs before development starts
What Location-Based Availability Covers
One catalog, several markets: the same product sold under different conditions depending on where the buyer is.
- Regional catalog visibility. Products and categories shown, hidden or restricted per country or region
- Country restrictions. Legal and licensing limits applied consistently in the catalog, the cart and at checkout
- Carrier-aware storefronts. Shipping options and services that follow the delivery address
- Address verification at checkout. Delivery data validated before any label exists, cutting failed deliveries
- Regional label flows. Correct labels and handover details for each destination’s requirements
- No-code administration. Visibility maps, restriction lists and carrier rules managed from settings screens your own team runs
How We Build It
Six architecture decisions that keep multi-market catalogs correct.
One Rules Engine, Many Scopes
Visibility decisions live in one engine, scoped by country, region, address or postcode, instead of conditionals scattered through templates and plugins.
The Address Beats the IP
Geolocation is a useful first guess at what a shopper should see, but the checkout address is the source of truth, and it is verified before anything ships.
Carrier Rules From the Source
Services, rates and delivery options come from each carrier’s own API per destination, so the storefront never promises a service the carrier can’t deliver.
Restrictions as Data
Country, category and product restrictions are explicit records you can test per destination, not hardcoded conditions that go stale when the law changes.
Regional Slices That Stay Fast
Per-market catalog views are built to work with page caching, so serving five countries does not mean five times the database queries.
Maintained as Carriers Change
Carrier APIs and regional rules keep moving. We maintain what we ship, so the integration changes with them instead of breaking at checkout.
Carrier integrations follow the same release discipline as the DHL and PostNL plugins we maintain, written down in our engineering standards. For new carrier or ERP connections, see WooCommerce Plugin Development & API Integration.
Proof: Location-Aware Commerce at Carrier Scale
The official PostNL plugin, rebuilt by Progressus on a new API.
PostNL’s previous WooCommerce integration, built by its parent company MyParcel, served Dutch customers only. Expanding to Belgium meant much more than adding a country to a list: a new API integration, a Belgian service catalogue driving the shipping options customers see, address verification at checkout, return shipments as a first-class feature, and a migration path so existing merchants could move over without disruption.
That’s the shipping side of the location problem, solved at carrier scale. Product-level visibility and restriction rules are built with the same approach; carrier work is simply where our location engineering is publicly verifiable today.
3,000+
active installations of the rebuilt official plugin
NL + BE
served by one plugin, with the Belgian service catalogue driving what customers see at checkout
0
major technical issues moving existing merchants from the old plugin to the new one
“We are very happy with Progressus, especially Shadi, as a WooCommerce integration partner. They keep the project organized, communicate clearly and understand the wishes well. We recommend Progressus to anyone who wants to develop a plugin for WooCommerce.”
Linda van der Mark, PostNL
Frequently Asked Questions
Can WooCommerce show different products per country?
Yes. Visibility is decided by explicit rules at product, category and cart level, scoped by country, region or address.
What about customers browsing through a VPN?
They’ll browse the catalog for the VPN’s country, which is harmless. What they can buy, and where it ships, is decided by the delivery address at checkout.
Do shipping options change automatically with the address?
Yes, when the rules come from the carrier’s own API. In the PostNL build, the Belgian service catalogue drives the options customers see for each delivery address, alongside address verification and return shipments.
Can one store sell across multiple countries?
Yes, that’s the normal case for merchants on the plugins we maintain: PostNL covers the Netherlands and Belgium, and the DHL plugin serves stores in several European and Asian markets. Each market gets its own visibility, carrier and restriction rules inside one store.
How are legal restrictions on products handled?
Restricted products are blocked at every step: hidden from the catalog where the law requires it and refused at cart and checkout for destinations they cannot ship to. Your team updates the lists when regulations change.
How is a location-based availability project priced?
As a fixed quote after scoping, based on the number of markets, carrier integrations and restriction types involved, not an hourly meter. Projects start at €2,500. You approve a written scope before we build.
Selling to Markets Your Catalog Can't Serve Yet?
Tell us where you sell, which carriers you use and which restrictions apply. You'll get a plain answer about what's involved and what it should cost.
What happens next
- Tell us which markets you serve today and which you want next. A call or an email is enough to start.
- We map visibility, restrictions, carriers and address checks for each destination.
- You get a written scope and a fixed quote (projects start at €2,500), or a straight answer if an existing plugin does the job.
Who you'll work with
