Product help

# Catalog Mobile webhook integration for ERP, stock, price and orders

Technical guide to publish products, sync stock and price, receive orders and operate the async webhook flow.

## What the integration solves

The webhook removes manual work from catalog publishing. Your ERP becomes the source of truth for products, stock, price and order capture.

- Publish products, prices and stock from one integration contract.

- Receive structured orders instead of fragmented chat messages.

- Give internal teams and partners one technical workflow to follow.

## How to structure the integration contract

The safest implementation keeps a stable external identifier, defaults to async processing and stores request_id for traceability.

- Use idMapeamento as the canonical identifier when possible.

- Persist request_id and final processing status.

- Keep commercial codes as an operational fallback, not as the primary key.

## Recommended operating routine

Treat publishing, status checks and error recovery as separate operational steps. That is what keeps the integration stable when pricing and stock change frequently.

- Schedule catalog sync windows with clear ownership.

- Refresh stock more often than the rest of the catalog payload.

- Create alerts for repeated failures on the same SKU or price table.

## Authorisation and contract limits

Use the integrationCode from the configuration and the idEcommerce assigned by support; idEcommerce identifies the integration source, not a product. The public contract requires cnpj, idEcommerce and tipo. Consult the current reference before implementation: individual requests, batches and photos have different limits.

## Will it work for my business?

### When should I store request_id?

Whenever the integration is async or your team needs reconciliation against the ERP log.

### Can I sync only stock and price?

Yes. Structural catalog sync and operational sync should run at different cadences.

### When should I contact support?

After you have the tested payload, the request_id and the exact route used, especially if the final status ends as failed or duplicate.

Guides

## Continue in product help

[All help guides →](https://catalogmobile.com/en/kb/)

---
Canonical: https://catalogmobile.com/en/kb/webhook-integration/
Language: en