Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.digifist.com/llms.txt

Use this file to discover all available pages before exploring further.

When Galantis syncs a product from Shopify, it maps the Shopify product data to a structured record stored in Galantis. This record is what powers WhatsApp product messages, automation condition evaluations, Back-in-Stock eligibility checks, and segment rules based on purchased collections or brands. Understanding what is synced — and what each field is used for — helps diagnose issues, build accurate segment rules, and manage which products appear in your WhatsApp catalog.

​
What this covers

  • All product fields synced from Shopify and their purpose in Galantis
  • How collection data is stored and used
  • The exclude_from_syncforce flag and when to use it
  • The full JSON payload storage via JSONB

​
Product fields

FieldSourcePurpose in Galantis
titleShopifyProduct name — displayed in SPM and MPM product cards, available as a template variable via order.product_name
descriptionShopifyFull product description — stored and available for catalog display
vendorShopifyBrand name — used in segment rules (Purchased brand) and catalog filtering
tagsShopifyProduct tags — used in the PRODUCT_IN_ORDER_HAS_TAG automation condition
imagesShopifyProduct images — displayed in product message formats and catalog browse; must meet Meta’s format requirements for Meta sync
Product tags deserve particular attention. They are the mechanism that connects Shopify’s product taxonomy to Galantis automation logic — the PRODUCT_IN_ORDER_HAS_TAG condition in automation flows evaluates these tags. If product tags are not consistently applied in Shopify, condition-based automation branching on product category will not work reliably.
Product images must be JPEG or PNG format and at least 500×500px to pass Meta’s validation during catalog push. Products with images that do not meet these requirements will fail on the Meta sync step. The images are stored correctly in Galantis regardless — the format requirement applies only to the Meta push. See Catalog Health.

​
The exclude_from_syncforce flag

The exclude_from_syncforce flag can be set on any individual product record in Galantis. When set, the product is excluded from being pushed to Meta during catalog sync operations. What it does:
  • Prevents the product from being included in Meta Catalog pushes (both initial push and incremental SyncMetaCatalogJob updates)
  • The product remains in Galantis — it is still synced from Shopify, still appears in your Galantis catalog, and still available for segment rules and automation conditions
  • The product will not appear in SPM, MPM, or Whole Catalog messages sent via WhatsApp
What it does not do:
  • It does not remove the product from Shopify
  • It does not prevent the product from being synced from Shopify into Galantis
  • It does not affect Back-in-Stock widget eligibility for the product’s variants
When to use it:
  • Products that are not ready for customer-facing WhatsApp commerce (draft products, internal SKUs, gift cards)
  • Products with images that fail Meta’s format requirements and cannot be fixed immediately — exclude them to prevent them from blocking the broader catalog push
  • Products that are available on your Shopify store but should not be surfaced in WhatsApp messages for business reasons (wholesale-only items, B2B products)
How to set it: Navigate to Catalog → [Product Name] and toggle the exclude flag on the product record. The flag takes effect on the next Meta sync operation.

​
Collection fields

Collections are synced into Galantis as separate records with their own webhook pipeline:
FieldSourcePurpose
titleShopifyCollection name
productsShopifyProducts associated with this collection
handleShopifyURL handle — used for collection-level deep links
Collection data is used primarily for segment rule evaluation (Purchased collection condition) and for organizing product selections in MPM templates into labeled sections.