Skip to content

Connections & discovery

Bring the right information into Flur. Reach where buyers are.

Catalogue connections supply product and service information into Flur. Outbound routes determine where that information can be discovered. These are separate operations — connecting a catalogue does not automatically enable every discovery route.

Inbound

Supply into Flur

These sources bring product and service information into Flur's catalogue layer.

Native catalogue

Direction: You add directly to FlurFreshness: Live — updated as you edit

Your own product and service records. Products need imagery, variants, price and inventory. Services need scope, duration, availability and booking information.

Shopify

Direction: Shopify → FlurFreshness: Synced — freshness depends on sync schedule

Connected product information from your Shopify store. Direction is inbound to Flur. Sync freshness and order write-back availability are shown in the connection settings.

Meta catalogue

Concept preview
Direction: Meta → Flur (direction supported)Freshness: Availability to be confirmed

Supported direction — inbound from your Meta product catalogue. Full availability and freshness details to be confirmed. Not yet operationally active.

Acuity Scheduling

Concept preview
Direction: Acuity → FlurFreshness: Calendar data — integration readiness to be confirmed

A scheduling platform. When supported, it supplies calendar and appointment information so Service Intent can match against real available slots. Integration readiness to be confirmed.

Outbound

Eligible routes to buyers

Where catalogued supply can be discovered — each route is governed and activated separately.

Catalogue connection and external visibility are separate operations. Connecting a source does not enable every outbound route.

Flur buyer conversations

Buyers interacting through Flur Commerce can discover and purchase catalogued products and services directly via conversational AI.

AI-assisted discovery experiences

Concept preview

Structured product and service information can be made understandable to supported AI-assisted discovery experiences where eligible. Availability is governed separately from catalogue connection.

Important distinctions

These are not the same operation. Understanding the difference matters for how you configure connections.

Syncing a catalogue ≠ appearing in every external channel

Connecting a catalogue source brings product or service information into Flur. Whether that information appears in a given external channel is a separate eligibility and activation decision.

Account information access ≠ payment permission

AIS connects your account data so Flur can understand your financial picture. It does not grant authority to initiate or authorise payments on your behalf.

A matched offer ≠ a completed purchase

The Opportunity Engine identifying a match between a saved intent and available supply is not a purchase. A person reviews the terms and approves before anything progresses.

Note on Acuity Scheduling

Acuity is a scheduling platform. When supported, it supplies calendar information so Service Intent can find a real appointment slot — rather than matching against unavailable times. Integration readiness to be confirmed. No booking or calendar access is active until the connection is explicitly enabled and confirmed.