Independent technical research by AumCreate. AumCreate is not the developer of Advanced Custom Fields and is not affiliated with WP Engine.
Short answer
ACF supports authenticated REST updates for field groups that have been exposed to the API. To synchronize an external product catalog or PIM, first enable the intended fields and post-type routes, then map stable external IDs, structured values and media references. Recurring synchronization also needs validation, field-ownership rules, idempotent writes and an explicit deletion policy.
What the native ACF REST integration provides
Advanced Custom Fields exposes opted-in field groups through WordPress REST endpoints. The ACF REST API guide states that field groups are not exposed by default and need the Show in REST API setting. Authenticated requests can update ACF data through supported endpoints. Those capabilities make external catalog ingestion possible, but they are not a complete PIM synchronization process by themselves.
A product information management system may own technical specifications, regulatory data, attachments and localized descriptions, while WordPress owns public page presentation and editorial overrides. Decide which system owns each field before creating an import. Otherwise an automated update can silently replace human edits.
Suggested approach
Confirm REST exposure and object identity
- Enable REST API visibility for each field group that is intentionally part of the integration.
- Ensure the target custom post type exposes its API route; for code-registered types, verify the WordPress show_in_rest setting.
- Inspect an authenticated GET response and OPTIONS schema for the target record before writing values.
- Choose a durable external product ID as the synchronization key rather than the displayed product title or URL slug.
- Use the minimum-permission integration user and keep write endpoints unavailable to anonymous requests.
WordPress documents show_in_rest for custom post types in its REST API handbook. If a field is missing, check both the field-group visibility and the post-type route before debugging the upstream PIM payload.
Mapping simple and structured fields
A scalar property such as manufacturer name or voltage is easier to map than repeatable specifications, images and relationships. ACF documents Repeater data in REST as an array of objects whose keys correspond to subfield names. This is a data-shape contract, not permission to assume that every installation has access to every field type; check the site's ACF edition and active field definitions.
| External PIM field | Suggested WordPress target | Validation before write |
|---|---|---|
| External product identifier | Dedicated immutable ACF field or controlled metadata | Nonempty and unique |
| Technical attributes | Typed ACF group or separate specification fields | Units, allowed values and required keys |
| Repeatable certificates or documents | Configured repeater or related attachment records | Row identity and valid media IDs |
| Product relationships | ACF relation or explicit reference mapping | Target items exist and are accessible |
| Localized copy | Language-specific content record where implemented | Locale and ownership policy |
Media and relationships must resolve to local objects
Do not send an arbitrary external image URL into a field expecting a WordPress attachment ID. Import media first through an authenticated and authorized workflow, preserve the PIM asset identifier, then use the resulting local reference. For relationship fields, resolve external references to existing WordPress record IDs, and defer unresolved links for a later pass.
Suggested approach
An incremental synchronization design
- Read changed records from the PIM using its documented export or API, recording source revision or modified time.
- Normalize field values and validate them against a versioned mapping contract. Preserve the original external product ID.
- Find an existing WordPress record by the external ID, otherwise create a draft under controlled rules.
- Write only PIM-owned fields through an authenticated path and leave editorially owned fields unchanged.
- Resolve attachments and references after their target objects exist; log unresolved dependencies.
- Track each run with source version, target ID, changed fields and failure reason so retries are idempotent.
Suggested approach
For deletions, decide separately whether the PIM should unpublish, archive or merely flag the WordPress record. A missing item in a partial feed must not automatically imply deletion. Preview destructive changes and retain a reconciliation report.
Suggested approach
Performance and field evolution
Large catalogs need bounded batches, pacing, targeted field reads and an exception queue. Changes to ACF field names, field types and PIM taxonomies should be reviewed as schema migrations rather than silently accepted. Test a representative sample that includes empty values, malformed units, deleted media, multilingual records and nested specifications.
Configuration or custom development
If editors only need to update a small set of fields manually, native ACF configuration and the REST interface may be enough. If the task involves recurring ERP or PIM updates, external IDs, media import, record dependencies and conflict resolution, build a dedicated sync service or WordPress plugin with explicit field ownership and audit logs. AumCreate can help design and implement that integration against the actual source and WordPress data models.
Sources
Product facts in this article are taken from the pages below.
- https://developer.wordpress.org/rest-api/extending-the-rest-api/adding-rest-api-support-for-custom-content-types/ — retrieved 2026-11-16
- https://www.advancedcustomfields.com/resources/wp-rest-api-integration/ — retrieved 2026-11-16
AumCreate is not affiliated with the vendors of the products discussed here. Product names and trademarks belong to their owners.
AumCreate