The milestone is distribution, not a badge
KaliCart Global has completed review and is published in the public plugin directory shared by ChatGPT and Codex. That gives the federated catalog a real user-facing distribution surface: people can invoke KaliCart in a conversation instead of first knowing a merchant domain, a REST route or an MCP endpoint.
OpenAI’s review does not make KaliCart an OpenAI product and it is not an endorsement of individual merchants. It means the submitted plugin met the directory requirements and can be discovered and used through that surface.
A path for catalogs beyond the standard US feed
OpenAI’s current product-feed documentation says that the standard OpenAI-format upload targets the United States. Extra markets require an integration whose countries and currencies have been explicitly configured by OpenAI. Product-feed onboarding is also limited to approved partners.
KaliCart Global does not pretend to change those rules. It provides a different path: a public plugin that searches KaliCart’s own consented index from inside ChatGPT. A participating Italian, German, French or Spanish WooCommerce store is not silently inserted into the native ChatGPT Commerce feed. Its eligible products become searchable through KaliCart Global, with the seller and source attached to every result.
Bridge and Global have different jobs
Participation is two explicit decisions
A merchant first chooses whether to join the Federated Catalog. That makes eligible catalog data available to KaliCart Global. Distribution to the OpenAI product-discovery channel is a second, separate authorization: it starts off, is never preselected and can be revoked without disabling the local Bridge.
The public plugin searches only that policy-scoped subset. It cannot expand a merchant’s authorization, enumerate a private catalog or use the merchant Bridge as an unrestricted discovery surface.
What a user can ask
- Find physical products across participating independent WooCommerce stores.
- Compare matching offers while retaining the seller on every result.
- Inspect why a product matched the request and when its indexed snapshot was produced.
- Verify one selected result against the merchant Bridge when that live read is available.
- Open the product on the merchant’s own storefront to complete the purchase.
KaliCart does not place orders, process payments or replace the merchant’s checkout. Search results are indexed snapshots; the storefront remains authoritative for payable price, current stock, shipping and the final transaction.
The catalog can survive a blocked API without pretending to be live
WooCommerce stores run on many hosting stacks, CDNs and firewall configurations. A public REST endpoint may be temporarily unreachable even when the merchant has not withdrawn consent. KaliCart’s architecture now separates those facts: signed catalog snapshots preserve bounded discovery, while signed installation identity and consent receipts preserve authorization. Live verification reports failure explicitly instead of converting an old snapshot into a current claim.
The engineering path from Bridge 1.0.138 through 1.0.141 is documented in the companion article, When a WooCommerce API is unreachable, the catalog should not disappear.
Try the public plugin
Open KaliCart Global in ChatGPT and ask it to search the participating catalog or list the merchants currently available through the network.