Real-time
Two-way sync
Changes in Box or Manhattan Associates WMS instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ ERP
Box to Manhattan Associates WMS integration — real-time, two-way sync
Keep Box and Manhattan Associates WMS in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
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
Why teams connect Box and Manhattan Associates WMS
Move the documents and data that Manhattan Associates WMS produces into Box as files, and let files stored in Box update the records they belong to in Manhattan Associates WMS, continuously and without exports or manual filing.
Manhattan Associates WMS runs the business on structured records: Distribution Orders, Purchase Orders & ASNs, Inventory, Items. Box holds files and the metadata that describes them: Tasks, Events, Files, Folders. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Manhattan Associates 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 Box, from signed contracts to vendor bills to receipts, describe a transaction Manhattan Associates 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 Distribution Orders, Purchase Orders & ASNs, Inventory, Items in Manhattan Associates WMS and Tasks, Events, Files, Folders in Box 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 Box already labeled and filed, and metadata captured against a stored file can create or update the matching record in Manhattan Associates 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 Manhattan Associates WMS and the file in Box never describe two different versions of the same document.
Common use cases
- 01 Reconcile ASNs and receipts with procurement systems to close POs automatically.
- 02 Feed labor and throughput data into analytics tools for DC performance reporting.
- 03 Mirror Metadata template instances on Files into database columns so contracts and assets are searchable and reportable alongside other business data.
- 04 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
Common sync patterns
Documents filed with their context
Files that Manhattan Associates WMS produces land in Box labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.
Metadata that files itself
Record fields from Manhattan Associates WMS, like customer, date, amount, type, and reference number, become the metadata and tags on the stored file in Box, so storage stays organized without anyone tagging by hand.
Where Box captures inbound files: details reach the record
A contract, vendor bill, or receipt added to Box with its details can create or update the matching record in Manhattan Associates WMS, so a document captured outside the finance system still reaches the books.
What you can sync between Box and Manhattan Associates 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.
| Box objects | Manhattan Associates WMS objects | How this pairing syncs | |
|---|---|---|---|
| Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. | Appointments Dock scheduling data coordinated with carriers and yard systems. | Folders is specific to Box and Appointments to Manhattan Associates WMS — each maps to any object or custom field on the other side. | |
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Distribution Orders Outbound order releases sent from the ERP or OMS into the WMS for waving and fulfillment. | Metadata is specific to Box and Distribution Orders to Manhattan Associates WMS — each maps to any object or custom field on the other side. | |
| Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. | Purchase Orders & ASNs Inbound expectations synced from procurement to drive receiving and putaway. | Collaborations is specific to Box and Purchase Orders & ASNs to Manhattan Associates WMS — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Inventory On-hand, allocated, and available positions read out across the DC network. | Users is specific to Box and Inventory to Manhattan Associates WMS — each maps to any object or custom field on the other side. | |
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Items Item master and packaging data kept consistent with the ERP catalog. | Groups is specific to Box and Items to Manhattan Associates WMS — each maps to any object or custom field on the other side. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Shipments & LPNs Ship confirmations, cartons, and tracking pushed back to order sources. | Tasks is specific to Box and Shipments & LPNs to Manhattan Associates WMS — each maps to any object or custom field on the other side. |
How changes propagate between Box and Manhattan Associates WMS
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.
Box Manhattan Associates WMS Sub-second propagation
DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.
DeliveryEach detected change is written to Manhattan Associates WMS through its API, with automatic retries and rate-limit backoff.
Manhattan Associates WMS Box Interval-based propagation
DetectionStacksync polls Manhattan Associates WMS for changes on an incremental schedule, reading only records changed since the previous pass. Polling on modified timestamps.
DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
What ships with Box ⇄ Manhattan Associates WMS
Connect Box and Manhattan Associates WMS for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Manhattan Associates WMS connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Manhattan Associates WMS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Box or Manhattan Associates WMS record.
Observability
Monitoring
Track your Box ⇄ Manhattan Associates WMS sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Box and Manhattan Associates WMS.
How the Box and Manhattan Associates WMS connectors work
Box
- Integration surface
- REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
- Authentication
- OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
- Change detection
- V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
- Capabilities
- read · write · webhooks
- Rate limits
- Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
Manhattan Associates WMS
- Integration surface
- REST API on Manhattan Active WM; database tables and message-based interfaces on legacy on-premises versions
- Authentication
- OAuth 2.0 on Manhattan Active; database credentials on legacy deployments
- Change detection
- Polling on modified timestamps; Manhattan Active also supports event/message-driven integration patterns
- Capabilities
- read · write
How it works
How to connect Box to Manhattan Associates WMS — three steps, no code
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.
- 01
Connect your apps
Authenticate Box and Manhattan Associates WMS with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Box
connected
Manhattan Associates WMS
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Manhattan Associates WMS 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.
objects · Box ⇄ Manhattan Associates WMSCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Box Manhattan Associates WMSCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Manhattan Associates WMS integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Manhattan Associates WMS: authenticate both systems, choose the objects to sync (such as Box's Folders and Metadata), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Box and Manhattan Associates WMS. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Box: V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed. On Manhattan Associates WMS: Polling on modified timestamps; Manhattan Active also supports event/message-driven integration patterns. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Manhattan Associates WMS side: Distribution Orders, Purchase Orders & ASNs, Inventory, Items, plus custom fields where Manhattan Associates WMS exposes them. On the Box side: Tasks, Events, Files, Folders. 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 Box and Manhattan Associates WMS: Documents filed with their context; Metadata that files itself; Where Box captures inbound files: details reach the record. Files that Manhattan Associates WMS produces land in Box labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.
SECURITY
Security teams trust Stacksync
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
→ SECURITY WITH BENEFITS
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 398 integrations available for Box and Manhattan Associates WMS.
Popular · 6 of 398
-
Box ⇄ TikTok Shop -
Box ⇄ Unleashed Software -
Box ⇄ NetSuite -
Manhattan Associates WMS ⇄ Amazon S3 -
Manhattan Associates WMS ⇄ Sharepoint -
Manhattan Associates WMS ⇄ Egnyte
No integrations match .
