Overview
Entities represent the individual data records that Junipeer has synced between your platforms — orders, customers, products, stock levels, and more. The Entities page lets you browse, search, and inspect these records.
You can find the Entities page in the left sidebar of any integration.
Entity list
The entity list is organized by data type. Use the tabs at the top to switch between entity types:
Articles — products/articles synced between platforms
Customers — customer records
Orders — orders, invoices, and related documents
Stock — inventory/stock level records
The exact tabs available depend on which flows are enabled for your integration.
Columns
Each entity in the list shows:
Status — the current sync state of the record.
Retriever Reference — the record ID in the source platform (the system data is being read from). For example, an order number from your e-commerce platform.
Storer Reference — the record ID in the target platform (the system data is being written to). For example, an invoice number in your ERP.
Children — the number of related sub-records (e.g., order line items within an order).
Last Updated — when this entity was last synced.
Entity detail page
Click on any entity to open its detail page. Here you can see:
Transaction history — a timeline of all sync operations that have touched this record, including when it was first created, when it was last updated, and any errors that occurred.
Raw data — the actual JSON payload that was sent or received. This is invaluable for debugging — if a field is not mapping correctly, you can inspect the raw data to see exactly what values were sent.
Retry — the ability to re-sync this specific record. Use this when a record failed to sync due to a temporary issue that has since been resolved.
Searching for entities
Use the search and filter tools to find specific records:
Search by reference number (either the source or target platform ID)
Filter by entity type using the tabs
Filter by status to find records that failed to sync
This is particularly useful when a customer reports an issue with a specific order — you can search by order number and see exactly what happened during the sync.
Understanding entity status
Synced successfully — the record exists in both platforms and the most recent sync completed without errors.
Error — the record failed to sync. Check the transaction history for details and resolve the underlying issue before retrying.
Pending — the record has been queued for syncing but has not yet been processed.
Tips
The entity list shows what Junipeer knows about — if a record exists in your source platform but does not appear here, it may not have been included in any sync (check your flow filters and time history).
Use the raw data view when working with Junipeer support to diagnose mapping issues.
The Retriever Reference and Storer Reference columns are the quickest way to answer "which target system record corresponds to which source record?" — but for a dedicated mapping view, see References.