Skip to content
FlurCommerce
Integration

Meta Catalogue

Synchronise relevant catalogue information with supported Meta catalogue environments. Connect your Flur Commerce product catalogue to Meta's catalogue infrastructure — keeping your product records consistent across platforms.

Important: Catalogue connectivity is not the same as permission to read or send Instagram or WhatsApp messages. These are separate, independently granted capabilities.

What the integration does

  • ✓Sends product records from your Flur Commerce catalogue to your linked Meta catalogue.
  • ✓Keeps product data (name, price, image, availability) consistent between Flur and Meta.
  • ✓Surfaces sync errors with clear explanations — failed syncs are visible, not silently hidden.
  • ✓Supports per-product retry when a specific record fails validation.

What it does not do

  • ✕Does not grant permission to send WhatsApp or Instagram messages — those require separate provider approval.
  • ✕Does not create promotional posts or ads on your behalf.
  • ✕A successful catalogue sync does not mean WhatsApp Business messaging is approved.
  • ✕Does not read your Instagram DMs or post to your Instagram feed.

Example: Adire Lagos

A fictional Lagos textile brand connects their Flur Commerce catalogue to their Meta catalogue.

1
Link Meta Business account

The merchant opens Commerce → Integrations → Meta Catalogue and authenticates with their Meta Business Manager account. Flur requests catalogue read/write permissions only.

2
Select target catalogue

Adire Lagos selects the specific Meta catalogue they want to sync into. A single Flur Commerce account connects to one Meta catalogue destination at a time.

3
Initial product push

Flur sends active catalogue items to Meta. Products with all required fields (name, price, image, availability, currency) sync immediately. Products with missing data enter "Needs attention" status.

4
Review sync results

The catalogue view shows each product with its last-attempt status. Green = good sync. Amber = needs attention with a specific explanation. The merchant resolves issues in the catalogue editor or in Flur Commerce.

5
Ongoing sync

When the merchant updates a product price or image in Flur Commerce, the change is pushed to the Meta catalogue on the next sync cycle.

Sync status illustration

Good sync and needs-attention status shown side by side. Failed syncs are always visible.

Good sync (green)
Adire Indigo Wrap
AL-AIW-001
Synced
Destination: Meta Commerce Catalogue
Needs attention (amber)
Tie-Dye Agbada Set
AL-TAG-003
Needs attention
Destination: Meta Commerce Catalogue
Issue: Product image does not meet Meta's minimum resolution requirement (500×500px). Update the image in the Flur catalogue editor and retry.

A "Needs attention" status is not the same as a permanent failure. Most issues are resolvable by updating the product record and retrying the sync.

Key distinctions

Catalogue sync, messaging and posts are separate things

Catalogue sync ≠ promotional post
Sending product data to Meta's catalogue does not create an Instagram or Facebook post. Your products appear in Meta's catalogue data layer — not on your feed or in Stories.
Good sync ≠ messaging approval
A green sync status means your product data reached Meta's catalogue successfully. It has no relationship to WhatsApp Business messaging approval, which is a separate process managed by Meta.
Connected logo ≠ everything works
An integration may show "connected" while individual product records still have sync issues. Check the per-product status, not just the connection banner.

Constraints and limits

Image requirements
Meta requires product images to meet minimum resolution (500×500px) and format rules. Products without compliant images will fail validation.
Supported fields
Only standard catalogue fields are synced. Custom Flur Commerce fields that have no Meta catalogue equivalent are not transmitted.
One catalogue destination
Each Flur Commerce account connects to a single Meta catalogue. Multi-catalogue setups require separate implementation.
Currency and pricing
Price fields must include a valid ISO currency code. Ambiguous pricing (e.g. negotiable) cannot be synced to Meta's catalogue format.

Frequently asked questions

Does this let me send WhatsApp messages to customers?
No. The Meta Catalogue integration only connects your product data to Meta's catalogue infrastructure. Sending WhatsApp messages requires a separately granted WhatsApp Business account permission — managed by Meta, not Flur.
What if a product has an unsupported field?
Fields that don't map to Meta's catalogue schema are skipped. The product can still sync successfully if all required fields are present. Only the supported field set is transmitted.
Is catalogue sync the same as posting to Instagram?
No. Catalogue sync puts your product data into Meta's catalogue layer. This is separate from Instagram posts, feed content, Shopping tags, or Stories — those require additional setup within Meta's tools.
What causes a 'Needs attention' status?
Common causes: missing or non-compliant product image, price field without a valid currency code, product name exceeding character limits, or a variant that fails Meta's field validation. The status message describes the specific issue.
How do I retry a failed product sync?
Fix the issue in your Flur Commerce catalogue editor, then click Retry sync on the affected product. Flur will attempt to push the updated record to Meta's catalogue on the next available cycle.

Connect your Meta catalogue

Keep your product data consistent across Flur Commerce and your Meta catalogue environment.

Get started