Two-way sync
Changes in Infor WMS or Xactly instantly reflect in both systems. No stale data, no manual imports.
Keep Infor WMS and Xactly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Xactly holds the customer relationship; Infor WMS runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Credits, Transactions (Commission & Bonus), Participants (Payees), Positions & Titles in Xactly with Shipments, Appointments, Items, Inventory in Infor WMS field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
Owners, territories, and org structure informed by Infor WMS stay current in Xactly.
A deal won in Xactly creates or updates the customer in Infor WMS with clean data, so fulfillment and invoicing start without re-entry.
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.
| Infor WMS objects | Xactly objects | How this pairing syncs | |
|---|---|---|---|
| Locations Bin and zone definitions scope inventory records during mapping. | Orders Sales order and transaction records loaded into Incent as the raw input for crediting and calculation; created and updated through Connect load and ETL steps (write) and read back for reconciliation, so read and write. | Locations is specific to Infor WMS and Orders to Xactly — each maps to any object or custom field on the other side. | |
| Shipments Ship confirmations and tracking references flow back to the order source system. | Credits Crediting records that tie an order to a participant and position; system-calculated credits are read, while manual and adjustment credits are loaded through Connect, so read and write. | Shipments is specific to Infor WMS and Credits to Xactly — each maps to any object or custom field on the other side. | |
| Appointments Dock appointment data coordinates carriers and yard operations with external schedules. | Transactions (Commission & Bonus) Calculated commission and bonus line items produced by Incent's calculation engine; read as the output of comp runs for reporting and downstream payout, so effectively read-only results. | Appointments is specific to Infor WMS and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side. | |
| Items Item definitions keep the WMS aligned with the ERP or OMS item master. | Participants (Payees) Sales reps and payees keyed to positions; loaded and updated from HRIS/HCM source data through Connect (write) and read for roster reporting, so read and write. | Items is specific to Infor WMS and Participants (Payees) to Xactly — each maps to any object or custom field on the other side. | |
| Inventory On-hand quantities by location feed available-to-promise in order-taking systems. | Positions & Titles Org-hierarchy positions and titles that credits and quotas roll up to; loaded and maintained through Connect (write) and read to resolve the hierarchy, so read and write. | Inventory is specific to Infor WMS and Positions & Titles to Xactly — each maps to any object or custom field on the other side. | |
| Receipts / ASNs Advance shipment notices and receipt confirmations sync with procurement systems. | Quotas / Targets Period quota and target values per position or plan; loaded from planning tools through Connect (write) and read for attainment reporting, so read and write. | Receipts / ASNs is specific to Infor WMS and Quotas / Targets to Xactly — 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.
DetectionInfor WMS notifies Stacksync of record changes through webhook events. ION event publishing or scheduled polling of API endpoints.
DeliveryEach detected change is applied to Xactly as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Xactly for changes on an incremental schedule, reading only records changed since the previous pass. No CDC log for external tools to consume.
DeliveryEach detected change is written to Infor WMS through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Infor WMS–Xactly connection.
Changes in Infor WMS or Xactly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Infor WMS or Xactly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Infor WMS or Xactly record.
Track your Infor WMS ⇄ Xactly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Infor WMS and Xactly.
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 Infor WMS and Xactly 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 Infor WMS and Xactly 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 Infor WMS and Xactly: authenticate both systems, choose the objects to sync (such as Infor WMS's Locations and Shipments), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Infor WMS: ION event publishing or scheduled polling of API endpoints. On Xactly: No CDC log for external tools to consume. Incremental sync uses SQL predicates on modified/last-updated timestamp columns (for example WHERE modified_date > watermark) against Connect's queryable objects, or scheduled Connect ETL Pipelines that pull deltas since the last run. Xactly Connect has no outbound HTTP webhooks, so change detection is pull/ETL-based. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Xactly side: Credits, Transactions (Commission & Bonus), Participants (Payees), Positions & Titles, plus custom fields where Xactly exposes them. On the Infor WMS side: Shipments, Appointments, Items, Inventory. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Infor WMS and Xactly: One customer master; Where Infor WMS manages people and org data: keep Xactly aligned; Where Infor WMS handles order-to-cash: closed-won flows through. Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
Infor WMS: REST API via the Infor OS / ION API gateway (cloud deployments run inside Infor CloudSuite). Authentication: OAuth 2.0 via Infor OS. Xactly: Xactly Connect REST API v2 (JSON), plus ODBC/JDBC drivers over the same ANSI-SQL data model. Incent data is exposed as SQL-queryable objects (for example xactly_order, xactly_credit, xactly_transaction, xactly_payment); data is loaded and extracted through Connect load/query steps and server-side ETL Pipelines. The base host is region/pod-specific (for example https://<pod>.xactlycorp.com). Authentication: OAuth 2.0 via the Xactly Connect API Gateway (bearer tokens issued on behalf of an Xactly Incent user), with HTTP Basic authentication using a dedicated Xactly Connect service-user's credentials also supported for the Connect REST API v2. The connecting user needs Connect/API access plus the relevant object permissions in Incent. Stacksync manages authentication, retries, and rate limits on both sides.
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 415 integrations available for Infor WMS and Xactly.