Two-way sync
Changes in Extensiv (3PL Central) or Pigment instantly reflect in both systems. No stale data, no manual imports.
Keep Extensiv (3PL Central) and Pigment in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.
Stacksync syncs Dimension lists, Tables, Scenarios, Data imports in Pigment with Items, Inventory, Orders, Receivers in Extensiv (3PL Central) in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Where Pigment serves a business unit and Extensiv (3PL Central) is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Invoices and payment activity from the billing side post through to the enterprise system automatically.
When one system is replacing the other, run both in parallel with records matching until the switch is complete.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Extensiv (3PL Central) objects | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Receivers Inbound receiving records (receipts/ASNs) that confirm stock arrival back to purchasing systems. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Receivers is specific to Extensiv (3PL Central) and Dimension lists to Pigment — each maps to any object or custom field on the other side. | |
| Shipments Carrier and tracking details synced back once orders ship. | Tables Row-based transactional data loaded into models from source systems | Shipments is specific to Extensiv (3PL Central) and Tables to Pigment — each maps to any object or custom field on the other side. | |
| Warehouses Facility records that partition inventory and order routing. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Warehouses is specific to Extensiv (3PL Central) and Scenarios to Pigment — each maps to any object or custom field on the other side. | |
| Inventory adjustments Manual stock corrections that reconciliation syncs need to capture. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Inventory adjustments is specific to Extensiv (3PL Central) and Data imports to Pigment — each maps to any object or custom field on the other side. | |
| Customers The 3PL's clients; nearly every other record is scoped to one, so syncs carry customer context on each call. | Users and permissions Access controls governing which model areas a sync can touch | Customers is specific to Extensiv (3PL Central) and Users and permissions to Pigment — each maps to any object or custom field on the other side. | |
| Items SKU masters kept aligned between the merchant's systems and the warehouse. | Applications Planning models organized by domain such as finance, sales, or workforce | Items is specific to Extensiv (3PL Central) and Applications to Pigment — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionExtensiv (3PL Central) notifies Stacksync of record changes through webhook events. Webhook events for order, receipt, item, and inventory changes, with polling on modified-date filters as a fallback.
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is written to Extensiv (3PL Central) through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Extensiv (3PL Central)–Pigment connection.
Changes in Extensiv (3PL Central) or Pigment instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Extensiv (3PL Central) or Pigment data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Extensiv (3PL Central) or Pigment record.
Track your Extensiv (3PL Central) ⇄ Pigment sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Extensiv (3PL Central) and Pigment.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Extensiv (3PL Central) and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Extensiv (3PL Central) and Pigment objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Extensiv (3PL Central) and Pigment: authenticate both systems, choose the objects to sync (such as Extensiv (3PL Central)'s Receivers and Shipments), map fields visually, and changes propagate both ways in milliseconds — no code required.
Extensiv (3PL Central): REST API. Authentication: Short-lived access tokens obtained from integration client credentials (client ID and secret). Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
Pigment: Pigment's model is multidimensional: metrics are sliced by dimension lists, so inbound records must map to those dimensions rather than flat columns. Extensiv (3PL Central): The REST API emits webhook events for order, receipt, adjustment, item, and inventory changes, so status updates can flow back without tight polling loops. Stacksync's field mapping accounts for these differences between Extensiv (3PL Central) and Pigment without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Extensiv (3PL Central) and Pigment records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Extensiv (3PL Central) and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Extensiv (3PL Central)–Pigment integration in-house.
Yes — Stacksync ships production-grade connectors for both Extensiv (3PL Central) and Pigment. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 312 integrations available for Extensiv (3PL Central) and Pigment.