Two-way sync
Changes in Infor WMS or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Keep Infor WMS and Sharepoint in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Infor WMS runs the business on structured records: Waves, Tasks, Locations, Shipments. Sharepoint holds files and the metadata that describes them: Drive items (document libraries), Columns and content types, Permissions and sharing, Site pages. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Infor WMS touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Sharepoint, from signed contracts to vendor bills to receipts, describe a transaction Infor WMS needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.
Stacksync keeps Waves, Tasks, Locations, Shipments in Infor WMS and Drive items (document libraries), Columns and content types, Permissions and sharing, Site pages in Sharepoint in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Sharepoint already labeled and filed, and metadata captured against a stored file can create or update the matching record in Infor WMS. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.
The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Infor WMS and the file in Sharepoint never describe two different versions of the same document.
A contract, vendor bill, or receipt added to Sharepoint with its details can create or update the matching record in Infor WMS, so a document captured outside the finance system still reaches the books.
As records change in Infor WMS, the corresponding files and metadata in Sharepoint are kept in step, so a stored document reflects the latest version rather than a stale one-time export.
Every transaction's supporting file lives in Sharepoint beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Infor WMS.
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 | Sharepoint objects | How this pairing syncs | |
|---|---|---|---|
| Inventory On-hand quantities by location feed available-to-promise in order-taking systems. | Columns and content types Field definitions and content types on a site or list; read the schema and create columns so database fields map cleanly onto SharePoint list fields. | Inventory is specific to Infor WMS and Columns and content types to Sharepoint — each maps to any object or custom field on the other side. | |
| Receipts / ASNs Advance shipment notices and receipt confirmations sync with procurement systems. | Permissions and sharing Role assignments and sharing links on sites, list items, and drive items; read and written to manage access, requiring Sites.Manage.All or Sites.FullControl.All scopes. | Receipts / ASNs is specific to Infor WMS and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side. | |
| Shipment Orders Outbound orders arrive from the ERP or OMS for allocation and picking. | Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. | Shipment Orders is specific to Infor WMS and Site pages to Sharepoint — each maps to any object or custom field on the other side. | |
| Waves Wave assignments group orders for fulfillment and can be reported outward. | Sites SharePoint site collections and subsites via /sites; read site properties and discover the document libraries (drives) and lists each site contains, addressed by hostname and site path or site ID. | Waves is specific to Infor WMS and Sites to Sharepoint — each maps to any object or custom field on the other side. | |
| Tasks Warehouse task data supports labor and productivity reporting in BI tools. | Lists Custom lists and libraries via /sites/{id}/lists; create and read lists along with their columns and content types so a target system can mirror or provision list definitions. | Tasks is specific to Infor WMS and Lists to Sharepoint — each maps to any object or custom field on the other side. | |
| Locations Bin and zone definitions scope inventory records during mapping. | List items Rows in a SharePoint list via /lists/{id}/items with a fields facet of column values; full create, read, update, and delete, synced two-way with database rows. | Locations is specific to Infor WMS and List items to Sharepoint — 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 written to Sharepoint through its API, with automatic retries and rate-limit backoff.
DetectionSharepoint notifies Stacksync of record changes through webhook events. Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last.
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–Sharepoint connection.
Changes in Infor WMS or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Infor WMS or Sharepoint 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 Sharepoint record.
Track your Infor WMS ⇄ Sharepoint sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Infor WMS and Sharepoint.
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 Sharepoint 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 Sharepoint 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.
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 383 integrations available for Infor WMS and Sharepoint.