Can you integrate IBM AS/400 with Infor WMS?

Explore a IBM AS/400 and Infor WMS integration with a Stacksync engineer. Stacksync support for IBM AS/400 and Infor WMS is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

Can IBM AS/400 and Infor WMS sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the IBM AS/400 and Infor WMS initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the IBM AS/400 account, edition, environment, and business objects the integration must access. Identify the Infor WMS account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the IBM AS/400 to Infor WMS sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map IBM AS/400 fields to Infor WMS?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a IBM AS/400 and Infor WMS integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the IBM AS/400 and Infor WMS pilot start with?

Start by reviewing Proposed product or catalog item table in IBM AS/400 (choose its name) in IBM AS/400 and Items in Infor WMS. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

Database / ERP · Two-way sync platform

IBM AS/400 and Infor WMS integration

Plan how IBM AS/400 and Infor WMS should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

IBM AS/400

Infor WMS

Review the integration scope

Built for teams where self-serve, reliability and scale matter

Case study

Migrated from MuleSoft

Case study

Migrated from Celigo

Migrated from Heroku Connect

Migrated from Matillion

Case study

Migrated from Fivetran

Case study

Migrated from Celigo

Proposed workflow

Product or catalog item reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving the proposed product or catalog item table in IBM AS/400 or Infor WMS Items needs a defined result in the other system.

Start with the proposed product or catalog item table in IBM AS/400 and Infor WMS Items. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve units, variants, categories, and applicable price lists before order lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest two variants of one product, a changed SKU, and a price that applies to only one market or currency.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between IBM AS/400 and Infor WMS
IBM AS/400 record	Infor WMS record	Record matching	Field ownership
Proposed product or catalog item tableProposed table; choose its name and schema.Reporting dataset	ItemsProposed record; confirm Stacksync object support.	Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.	Assign ownership for catalog content, price, and stock separately.
Proposed inventory or stock position tableProposed table; choose its name and schema.Reporting dataset	InventoryProposed record; confirm Stacksync object support.	Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient.	Choose the stock authority and distinguish available, reserved, and physical quantities.
Proposed shipment or fulfillment tableProposed table; choose its name and schema.Reporting dataset	Shipment OrdersProposed record; confirm Stacksync object support.	Retain shipment/fulfillment and line IDs, order reference, and carrier context.	The fulfillment owner controls shipped quantities and cancellation eligibility.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

IBM AS/400

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Libraries Physical files (tables) Logical files (views) Members Rows / records Journals and journal receivers	Confirm support for this record type and the direction you need.

Discuss IBM AS/400 requirements

Infor WMS

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Items Inventory Receipts / ASNs Shipment Orders Waves Tasks	Confirm support for this record type and the direction you need.

Discuss Infor WMS requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits

Connection requirement	IBM AS/400	Infor WMS
Integration interface	SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access	REST API via the Infor OS / ION API gateway (cloud deployments run inside Infor CloudSuite)
Authentication	Confirm the credentials, API plan, and permissions required for IBM AS/400.	Confirm the credentials, API plan, and permissions required for Infor WMS.
Change detection	Confirm how Stacksync detects changes for this connector and the objects you need.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Confirm with Stacksync	Confirm with Stacksync
Write access	Confirm with Stacksync	Confirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

IBM AS/400

Integration interface: SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access
Authentication: Confirm the credentials, API plan, and permissions required for IBM AS/400.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the IBM AS/400 account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for IBM AS/400, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for IBM AS/400 and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Infor WMS

Integration interface: REST API via the Infor OS / ION API gateway (cloud deployments run inside Infor CloudSuite)
Authentication: Confirm the credentials, API plan, and permissions required for Infor WMS.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the Infor WMS account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Infor WMS, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for Infor WMS and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare IBM AS/400 and Infor WMS access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

IBM AS/400 setup checklist

Identify the IBM AS/400 account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for IBM AS/400, including read/write support, authentication, and initial-load limits.

Infor WMS setup checklist

Identify the Infor WMS account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Infor WMS, including read/write support, authentication, and initial-load limits.

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the IBM AS/400 and Infor WMS planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Reporting dataset

Proposed product or catalog item table in IBM AS/400 (choose its name) / Items

Plan a product or catalog item dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

IBM AS/400: Your database schema
Infor WMS: Object support to establish
Record identity: Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Field ownership: Assign ownership for catalog content, price, and stock separately.

Fields to include

Source product ID
SKU or variant reference
Description
Unit of measure
Price-list reference

Record dependencies: Resolve units, variants, categories, and applicable price lists before order lines.
Validation: Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Recovery: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

Reporting dataset

Proposed inventory or stock position table in IBM AS/400 (choose its name) / Inventory

Plan a inventory or stock position dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

IBM AS/400: Your database schema
Infor WMS: Object support to establish
Record identity: Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient.
Field ownership: Choose the stock authority and distinguish available, reserved, and physical quantities.

Fields to include

Product reference
Location reference
Quantity type
Quantity
As-of time

Record dependencies: Resolve product, unit, warehouse/location, and lot/serial references.
Validation: Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
Recovery: Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.

Reporting dataset

Proposed shipment or fulfillment table in IBM AS/400 (choose its name) / Shipment Orders

Plan a shipment or fulfillment dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

IBM AS/400: Your database schema
Infor WMS: Object support to establish
Record identity: Retain shipment/fulfillment and line IDs, order reference, and carrier context.
Field ownership: The fulfillment owner controls shipped quantities and cancellation eligibility.

Fields to include

Source shipment ID
Order/line references
Carrier
Tracking reference
Fulfillment status

Record dependencies: Resolve order lines, delivery address, carrier, and any partial-fulfillment references.
Validation: Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.
Recovery: Verify existing fulfillment before retrying creation; reconcile quantities against order lines.

Reporting dataset

Proposed task or work item table in IBM AS/400 (choose its name) / Tasks

Plan a task or work item dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

IBM AS/400: Your database schema
Infor WMS: Object support to establish
Record identity: Use a stable task/work-item ID and preserve its project or parent-ticket reference.
Field ownership: Choose the owner of task status and assignment; destination workflow states may require an explicit transition.

Fields to include

Source task ID
Parent reference
Assignee
Status
Due date

Record dependencies: Resolve project, user, and parent-item references before the task.
Validation: Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones.
Recovery: Reconcile the destination state before retrying a transition to avoid reopening completed work.

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Proposed product or catalog item table in IBM AS/400 (choose its name) / Items to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your IBM AS/400 and Infor WMS record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Proposed product or catalog item table in IBM AS/400 (choose its name) / Items, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when IBM AS/400 and Infor WMS need a transformation, approval, or action outside a direct record sync.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit: Consider for a one-time IBM AS/400 / Infor WMS migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Product or catalog item reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Proposed product or catalog item table in IBM AS/400 (choose its name) or Items record needs a defined result in the other system.

Start with IBM AS/400 Proposed product or catalog item table in IBM AS/400 (choose its name) and Infor WMS Items. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve units, variants, categories, and applicable price lists before order lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.

If it fails: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

Inventory or stock position reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Proposed inventory or stock position table in IBM AS/400 (choose its name) or Inventory record needs a defined result in the other system.

Start with IBM AS/400 Proposed inventory or stock position table in IBM AS/400 (choose its name) and Infor WMS Inventory. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve product, unit, warehouse/location, and lot/serial references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test the same SKU in two locations, a reservation, and an older snapshot arriving late.

If it fails: Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.

Shipment or fulfillment reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Proposed shipment or fulfillment table in IBM AS/400 (choose its name) or Shipment Orders record needs a defined result in the other system.

Start with IBM AS/400 Proposed shipment or fulfillment table in IBM AS/400 (choose its name) and Infor WMS Shipment Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve order lines, delivery address, carrier, and any partial-fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.

If it fails: Verify existing fulfillment before retrying creation; reconcile quantities against order lines.

Reconcile Infor WMS business records with IBM AS/400

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in Infor WMS needs operational visibility through Physical files (tables) or Logical files (views).

Select Items or Inventory with the correct legal entity, period, and currency.
Define a reporting relationship in IBM AS/400; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Proposed product or catalog item table in IBM AS/400 (choose its name) / Items

Test case

Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.

Expected result

The expected product or catalog item relationship is preserved with no duplicate action or unintended write.

Proposed inventory or stock position table in IBM AS/400 (choose its name) / Inventory

Test case

Test the same SKU in two locations, a reservation, and an older snapshot arriving late.

Expected result

The expected inventory or stock position relationship is preserved with no duplicate action or unintended write.

Proposed shipment or fulfillment table in IBM AS/400 (choose its name) / Shipment Orders

Test case

Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.

Expected result

The expected shipment or fulfillment relationship is preserved with no duplicate action or unintended write.

Proposed task or work item table in IBM AS/400 (choose its name) / Tasks

Test case

Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones.

Expected result

The expected task or work item relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated product or catalog item change

Investigate

Inspect IBM AS/400 Proposed product or catalog item table in IBM AS/400 (choose its name) and Infor WMS Items, their IDs, and the destination error.

Next action

Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

Rejected or repeated inventory or stock position change

Investigate

Inspect IBM AS/400 Proposed inventory or stock position table in IBM AS/400 (choose its name) and Infor WMS Inventory, their IDs, and the destination error.

Next action

Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.

Rejected or repeated shipment or fulfillment change

Investigate

Inspect IBM AS/400 Proposed shipment or fulfillment table in IBM AS/400 (choose its name) and Infor WMS Shipment Orders, their IDs, and the destination error.

Next action

Verify existing fulfillment before retrying creation; reconcile quantities against order lines.

A record type or update is unavailable

Investigate

Check the IBM AS/400 and Infor WMS connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between IBM AS/400 and Infor WMS

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

IBM AS/400 Infor WMS Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Infor WMS.

Infor WMS IBM AS/400 Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in IBM AS/400.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ