Use case: syncing content with Adobe Commerce without editing the store by hand

By Manuel Mattar3 min read

In short

This is an example scenario. An Adobe Commerce store installs the Bruxel_Sync module, which sends its products to Bruxel and receives the published content back in the attributes and store views it mapped. The store remains the owner of the catalog and Bruxel only writes the description.

This case is an example, not a customer: an imaginary store and a scenario catalog to show how the Bruxel_Sync module works from start to finish. The versions, permissions and safeguards are the ones in today's help guide.

The situation

A home goods store sells 4,000 products on Adobe Commerce 2.4.8, with two store views: one in Spanish and one in English. Descriptions are written by a two-person team, pasted into the Magento admin product by product and translated afterwards. When a season arrives, the catalog grows faster than the team.

The store wants to generate content in Bruxel and have it reach the right product, in the right language, without overwriting what already works.

What travels, and in which direction

Before installing anything, the team understands the module's rule: two things travel, each in one direction.

  • From the store to Bruxel: the products —SKU, name, category and the attributes they choose—. It is the raw material for generating. Enabled and visible products travel; hidden variants of a configurable product stay out, so as not to spend credits on pages the store does not show.
  • From Bruxel to the store: the content already published, written to the product page, in each language's store view.

The store owns the catalog. If someone edits a name or a category in Bruxel, the next send from the store overwrites it.

Step 1: the key and the installation

An administrator creates a key in Channels → API keys with catalog, attributes and export permissions. Then the store's developer installs the module with Composer. The module is installed turned off: nothing moves until it is enabled.

In the Magento admin, under Stores → Configuration → Bruxel → Sincronización, the developer does the four steps:

  1. Paste the key. "Test connection" confirms it responds and which account it reaches.
  2. Map each language to its store view: Spanish to the Spanish view, English to the English one.
  3. Choose which attributes travel to Bruxel as context for generating: material, dimensions, color.
  4. Map the content fields: which Bruxel field is written to which Magento attribute.

Step 2: generate and publish in Bruxel

With the products in Bruxel, the team sets up its brand voice and generates in batches from the catalog. In a batch, each product costs 7 credits per output language; with two languages, 14. What gets published in Bruxel is what the module will write; if the organization has approval turned on, nothing goes out without an administrator approving it.

Step 3: the first sync, without scares

The first write over a catalog that already has descriptions is the delicate moment. The module ships with two safeguards, and the team uses them:

  • Test mode shows what would change —product, field, store view, current and new value— without writing anything.
  • An option turned on by default that does not overwrite fields that already have text and that Bruxel never touched.

Also, before writing a field for the first time, the module saves the previous value, and a restore command brings it back exactly as it was. Before the first large sync, the developer sets the indexers to "Update on Schedule", because each write invalidates that page's cache.

Step 4: the real-time notification

For the store to learn the moment something is published, the administrator registers the module's address in Channels → Webhooks, subscribed to the description-updated event. She does it after enabling the module and pasting the secret: if the endpoint fails several times in a row, Bruxel deactivates it on its own. Even if the webhook fails, the content still arrives, because the module checks on its own every hour.

What gets solved and what does not

Solved: the team no longer copies and pastes descriptions into Magento. The module only writes to the store-view-scoped text attributes it mapped, never changes the product URL and never deletes: an empty field or an unpublished product leave the page as it is.

Not everything is solved:

  • Images do not travel to the store in this version.
  • Several websites in the same store require checking the mapping by hand.
  • Adobe Commerce as a Cloud Service is not covered; Adobe Commerce or Magento Open Source 2.4.7, 2.4.8 and 2.4.9 are.
  • Content Staging: a scheduled campaign that gets applied overwrites what Bruxel wrote; you have to publish again afterwards.
  • The languages it syncs are Spanish, English, French and Portuguese.

The Adobe Commerce and webhooks guides have the full setup. The integrations, channels and AI content pages show the rest of the path.

Frequently asked questions

Does Bruxel log into my Magento?

No. The module is installed in your store and it is the one that calls Bruxel. Bruxel never goes into your Magento.

What happens if I edit the product name in Bruxel?

The store owns the catalog: the next send from the store overwrites the name, brand, category and attributes. What Bruxel sends to the store is the generated content, and nothing else.

Does the module upload images to the store?

Not in this version. Images do not travel to the store; the module only writes the text content to the attributes you mapped.

Sources

  1. Magento (Wikipedia)
  2. Webhook (Wikipedia)

About the author

Manuel Mattar

Founder of Bruxel.AI

In 2014 he founded Wolf Sellers, an e-commerce agency in Mexico City, and later Bruxel.AI, the AI-powered PIM.

See all posts by Manuel Mattar

Try it with your catalog

Create your free account and try Bruxel with your own products using the welcome credits.

Keep reading

Use case: syncing content with Adobe Commerce without editing the store by hand