Connect Commercetools with MetaPack to calculate live shipping rates, show delivery options at checkout, and automate label creation across carriers, with tracking synced back to customers.
• Product, variant, category, and attribute data is read from commercetools APIs and transformed into Meta Catalog feed fields used by Meta Commerce Manager.
• Price, currency, and locale-specific values are mapped to Meta’s required formats, with per-market handling for titles, descriptions, and URLs where available.
• Inventory and availability signals are synced based on commercetools stock data and channel or supply configuration, with out-of-stock rules applied before export.
• Asset URLs for images are resolved per variant, validated for reachability, and included in the Meta item payload to meet feed requirements.
• Delta sync logic sends only changed products and variants on scheduled runs, while full refreshes rebuild the catalog when large structural changes occur.
• Validation errors, rejections, and field-level mapping issues are logged with item identifiers, allowing trace-back to the originating commercetools records.
.png)
We map commercetools products, variants, pricing, and stock into Meta’s required fields, then run scheduled or near-real-time updates through a feed and API sync. This helps keep availability and pricing consistent across your ads and storefront.
Yes, the sync layer can enrich and validate attributes, deduplicate variants, and enforce Meta formatting rules before data reaches Commerce Manager. You get fewer disapprovals and cleaner product sets for Advantage+ Shopping and dynamic ads.
It can, as long as store, channel, and price selection rules are defined up front. We configure per-market feeds so each Meta catalog receives the right currency, language, and availability.
Typically you need product identifiers (SKU and optionally GTIN/MPN), titles, images, URLs, pricing, and stock signals, plus category and brand where available. We also align variant attributes so Meta can group items correctly.
Most timelines depend on catalog size, attribute quality, and the number of markets, but the first usable feed is usually the fastest milestone. We validate in staging, run catalog QA against Meta’s diagnostics, and only then switch on production sync.














