Booking and shipment preparation
Extract the request, match the customer and prepare the fields needed for the agreed booking or shipment operation. Keep a quote, booking and shipment distinguishable.
Explore this workflowAI Operators · TMS
Shipflow for Magaya
Explore Magaya Open API workflows for shipment intake, document validation and invoice preparation. Map records, permissions and completion checks with Shipflow.
Configured for your environment. Available interfaces, accessible records and permitted actions depend on your product edition, account permissions and agreed workflow.
Discuss your Magaya workflowConfigured around your environment. Governed by your SOPs.
- Vendor interface
- Magaya Open API web services; supported operations depend on your deployment.
- Operational context
- Shipment records, bookings, document attachments and invoice references.
- First scope
- One record type, explicit matching rules and a verified update or review package.
Where integration creates value
Keep shipment records connected to the documents around them.
A revised shipping instruction may require several checks before it belongs in Magaya: which shipment it concerns, whether the revision supersedes another document and which differences require approval. Copying fields without that context can introduce a second version of the same problem.
Shipflow’s proposed integration workflow links authorized incoming documents to a defined Magaya operation. Start with the shipment reference and the expected result. This could be a validated record proposal, a document discrepancy or an invoice review package rather than an unrestricted update across the platform.
Workflow opportunities
Start with the work you want to complete.
Document-to-shipment checks
Compare document fields with the matched shipment or another authorized document. Preserve versions and flag differences before proposing a record update.
Explore this workflowInvoice evidence preparation
Associate incoming invoice data with the relevant shipment references and supporting documents. Separate a matched evidence package from a posted or paid invoice.
Explore this workflowIllustrative workflow · subject to agreed scope
From a revised instruction to a validated shipment record
Illustrative workflow: the operations team receives a revised shipping document for a shipment already maintained in Magaya.
Find the right record
Extract references and resolve the shipment through the permitted interface. Raise duplicate or missing matches for review.
Compare the revision
Identify changes in the agreed fields and compare them with the previous document and accessible record context.
Prepare the approval package
Show the proposed changes with their source and reason. Keep commercial or operational changes outside authority pending a decision.
Verify the agreed result
Apply an approved action only through a supported operation. Confirm its record reference and preserve any rejected fields as unresolved work.
Connection approach
Confirm the interface before the promise.
Magaya describes its Open API as a collection of web services and lists examples including bookings, shipments, invoices, document attachments and shipping events. These identify relevant data areas; they do not prove every field or write operation is available in your installation.
Confirm the actual service documentation, version, authentication, object identifiers and enabled operations with your Magaya administrator. Scope required lookups separately from record creation or modification. Existing middleware can remain in the design if it provides the agreed mapping and response handling.
Setup requirements
What we confirm with your team.
Version and service access
Identify the Magaya deployment, API provisioning, administrator and approved test environment.
Object and attachment rules
Agree shipment identifiers, document types, version handling and how attachments are associated with a record.
Source-of-truth policy
Define which source wins when the instruction, existing shipment and customer master disagree.
Update acceptance tests
Test missing references, repeated attachments, changed document versions and operations that fail after partial processing.
Control and rollout
Make access and accountability explicit.
Avoid duplicate records
Reconcile incoming requests against existing work before creating a shipment or invoice proposal.
Keep changes reviewable
Retain the previous value, proposed value and document evidence wherever a business decision is required.
Keep finance authority separate
An invoice comparison does not authorize posting, changing supplier details or releasing a payment.
Common questions
Before connecting Magaya.
Does the public Open API page prove Shipflow support?
No. It establishes a vendor integration route to investigate. Shipflow’s connection and the required operations must be validated in your environment.
Can document comparison be the first workflow?
Yes. A bounded comparison and review package can be scoped before enabling any record writes, with clear matching and escalation rules.
Are warehousing and customs included automatically?
No. Those processes require their own records, permissions and acceptance criteria even if they are part of the same Magaya environment.
How do we test the result?
Use representative document revisions and verify the resulting records, not just extraction accuracy. Track false matches, rejected changes and human rework.
Product names identify the systems discussed. This page does not imply vendor certification, partnership or endorsement. Supported actions and the implementation scope are confirmed with your team.
Start with a defined scope
Bring your workflow.
Keep your Magaya environment.
Map the inputs, system access and approval boundaries with Shipflow. Agree on a useful first integration and how to verify its result.
Book a working session