One model, many channels
What is maintained once is available everywhere, without copies that drift apart unnoticed.
CoreX holds locations, brands, products, services and contacts as linked objects, the verified source that publishers, local pages, posts and AI systems draw their information from.
Schematic excerpt of the field model, the product includes further fields.
A slowly rotating sphere of the field names CoreX tracks for a location, from address and opening hours through categories and services to reviews and sync status.What is maintained once is available everywhere, without copies that drift apart unnoticed.
Required fields, value ranges and approvals make sure only verified details go out.
Service descriptions, images and text blocks exist once and are used per location.
API, webhooks and exports make the records usable for your own systems, outside Balu too.
One record in CoreX becomes the location page, the post and the publisher profile. The information is not copied but used, which is why it cannot drift apart.
Brand, location, service, product, review, contact, linked, versioned and with valid-from dates.
Which fields are set centrally and which the location may maintain itself.
Images assigned to brand, location or service; formats for each publisher.
Schema.org-compliant data for local pages and machine-readable sources for AI systems.
Which objects and fields your organisation keeps, standard or extended.
Import from existing systems, merging of duplicates.
Required fields, approvals and ownership per level.
Modules and interfaces read the same records.
CoreX draws its data from the same source as every other module, and returns its results there.
In the demo we work with one of your locations, including a check of its current data.