Akeneo

The product information manager. It describes what a product is; it says nothing about what it sold for or cost, which comes from NetSuite.

What it delivers

Categories, attributes, brands, products and SKUs.

Cadence and window

The daily reset queues catalogue work; frequent cron invocations drain it. Products and their per-domain rows are staged and swapped together, and SKU work follows that swap. Attributes and translation tables also use staged refreshes.

Not every Akeneo table is replaced. productbrands and productcategories are upserted to retain their identities; their language tables are swapped. CCC's top-level reporting category mapping comes from reference configuration, which the category job reads rather than imports.

A staged product fetch is not visible until its swap. Upserted reference rows can become visible during a run. The feed supplies current values, not an attribute-change history.

Quirks and limits

• Authentication uses a token with a short life, cached by CCC and refreshed as needed. A cached token is runtime state, not stale data.
• A product present in Akeneo but absent from NetSuite, or the reverse, is normal rather than an error. The two systems describe overlapping but different populations.

Where it lands

products, productdomains, productskus, and the category, brand, attribute and translation tables. See products for their relationships.

Related

• Products
• PriceShape for prices, which Akeneo does not supply

Evidence

Refresh behaviour from app/jobs/akeneo/getproducts.php, getproductskus.php, getcategories.php, getbrands.php and getattributes.php. Feed list from AGENTS.md, The application. Swap pattern and the healthcheck sitting on the swap step from AGENTS.md, Models and database and Jobs. Token caching from the tokens table note in AGENTS.md. Basis: code-checked against the current implementation.