Connect & Manage Product Catalogs
Connect supported catalogs and use current product IDs, prices, images, and availability in conversations and automation.
STEPS
- Confirm the business owns the supported catalog.
- Authorize the provider account.
- Select the catalog and connect it to the correct workspace and channel.
- Synchronize products.
- Review IDs, names, prices, media, and availability.
- Test product use in Smart Inbox, automation, and order workflows.
Do not let AI promise stock or price without current confirmation.
Who should use it
Workspace owners, operations teams, sales users and authorized technical users.
Where to find it in Wemblo
Wemblo -> Marketing -> Catalogues
Before you begin
- Use the correct workspace and authorized role.
- Prepare fictional Pakistan test data.
- Confirm connected provider accounts where required.
- Define who approves price, stock, booking, payment or final status.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Catalog | Product collection. |
| Product ID | Stable product identifier. |
| Price | Current approved amount. |
| Availability | Current stock or sale status. |
| Sync | Update from the connected source. |
Test and verification
- Complete one successful path with fictional data.
- Complete one invalid, failure or permission path.
- Confirm the result appears in the correct workspace and module.
- Confirm the correct person or team can review and continue the work.
Common issues and solutions
| Issue | What to Check |
|---|---|
| Configuration does not save | Required fields, validation, permission and active workspace. |
| External action fails | Credential, provider status, endpoint or field mapping. |
| Duplicate record or action | Event ID, idempotency, retries and existing record. |
| Customer notification is missing | Template, channel connection, status transition and contact details. |
Security, privacy, consent, cost and provider notes
- Use only data the business is authorized to process.
- External provider charges, policies, approvals, limits and availability remain separate.
- Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
- Use human review for sensitive, regulated, urgent, financial or final decisions.
Last reviewed: