Quick answers
- Can SignalEDI help me connect to Mirakl?
- SignalEDI helps prepare mappings, sample validation, and the workflow required for your Mirakl program. Scope is confirmed during setup. Production connection requires the applicable partner approval; this guide is not evidence of a live connection or certification.
- What determines the Mirakl onboarding timeline?
- The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule. Agree the schedule after requirements and testing scope are confirmed. This is not a guaranteed go-live date.
- Which ERP systems can I use for Mirakl?
- Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
Plan the integration workflow
SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.
1. Your business system
Identify the source records, system edition, data owner, and allowed access.
2. SignalEDI preparation
Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.
3. Partner testing and approval
Complete the partner-controlled tests and retain permission before enabling live exchange.
Conceptual workflow only. A diagram or catalog listing does not establish certification or an active production connection.
Build your onboarding checklistScope the workflow before choosing a plan
Use the published plans as a starting point. Confirm the supported marketplace operations, connector scope and any add-ons separately; trial access does not prove a production-ready Mirakl connection.
- Starter
- $199/mo
- 1,000 transactions / mo · 5 trading partners
- Growth
- $999/mo
- 10,000 transactions / mo · Unlimited trading partners
30-day Growth evaluation. No credit card to start. Paid add-ons are excluded; choose a paid plan at production go-live or after the trial to continue.
See all plans and usage chargesStart with one marketplace and one clear workflow.
Bring your account role, operator instructions and system requirements. Review the supported path and acceptance criteria before committing to a rollout.
SignalEDI is an independent provider, not endorsed by Mirakl. Marketplace approval, certification and connector availability must be confirmed for the specific project.
Public sources reviewed 2026-11-09
What the public record confirms
- Mirakl Connect documents APIs for products, inventory, orders and shipments across a seller's stores. Mirakl Platform separately documents seller, operator and front APIs. Establish which product and role your project uses before selecting endpoints. A capability available to an operator is not automatically available to a seller, and a channel-platform connector differs from a seller's ERP connection.
- Mirakl Platform documentation limits its webhooks and cloud events to operator users. A seller-side design should verify its supported update mechanism rather than promise event-driven synchronization. Agree how changes are detected, how often they are collected, how failures are retried and how older updates are reconciled. Do not describe scheduled imports as real-time delivery without evidence.
- Keep marketplace objects distinct from EDI transaction sets. An order, shipment record or uploaded invoice does not become an X12 850, 856 or 810 merely because its business purpose sounds similar. Where an ERP requires EDI, document the transformation between its agreed implementation guide and the selected Mirakl interface, including identifiers, quantities, taxes, currency and permitted state changes.
- Mirakl's public materials describe API and file-based connectivity, including EDI and SFTP for custom setups. These describe Mirakl's offering, not a verified SignalEDI implementation or an entitlement for every account. Confirm access, supported operations, commercial arrangements and testing requirements for the specific project. A platform listing does not establish partnership or certification.
- As reviewed November 9, 2026, SignalEDI's status notice identifies a pause in production outbound X12 810 invoices, 855 order acknowledgments and 856 shipping notices. Sandbox tests and inbound documents are unaffected by that pause. This is a scoped SignalEDI delivery restriction, not a statement that all Mirakl APIs or integrations are paused. Check current status before planning production delivery.
Document and workflow scope
Use the cited source boundaries below, then confirm your current assigned program: Exact specifications come from your partner packet. Treat this as a planning checklist, not a substitute for the current implementation guide.
- Marketplace and account scope: record the operator, store identifiers, account role, approved API product and test environment. Keep credentials separate from project notes, and identify who can authorize production activation.
- Catalog and offer mapping: distinguish product descriptions from commercial offers, including seller SKU, marketplace identifiers, price, currency, stock and availability. Record field ownership and how rejected content is corrected before publication.
- Order and fulfillment mapping: retain marketplace order and line references through acceptance, allocation and shipping. Define partial quantities, tracking values and permitted cancellation behavior. Verify the outcome of each business operation.
- Returns, invoices and reconciliation: identify interfaces in scope and which system owns refunds and financial records. Uploading an invoice document does not prove payment settled or a separate EDI invoice was accepted.
Connectivity and testing requirements
Connectivity
Confirm whether the current Mirakl program uses AS2, SFTP, VAN, or another named transport.
Onboarding window
Not verified on this page.
Certification focus
The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule.
- Mirakl Connect documents APIs for products, inventory, orders and shipments across a seller's stores. Mirakl Platform separately documents seller, operator and front APIs. Establish which product and role your project uses before selecting endpoints. A capability available to an operator is not automatically available to a seller, and a channel-platform connector differs from a seller's ERP connection.
- Mirakl Platform documentation limits its webhooks and cloud events to operator users. A seller-side design should verify its supported update mechanism rather than promise event-driven synchronization. Agree how changes are detected, how often they are collected, how failures are retried and how older updates are reconciled. Do not describe scheduled imports as real-time delivery without evidence.
- Keep marketplace objects distinct from EDI transaction sets. An order, shipment record or uploaded invoice does not become an X12 850, 856 or 810 merely because its business purpose sounds similar. Where an ERP requires EDI, document the transformation between its agreed implementation guide and the selected Mirakl interface, including identifiers, quantities, taxes, currency and permitted state changes.
- Mirakl's public materials describe API and file-based connectivity, including EDI and SFTP for custom setups. These describe Mirakl's offering, not a verified SignalEDI implementation or an entitlement for every account. Confirm access, supported operations, commercial arrangements and testing requirements for the specific project. A platform listing does not establish partnership or certification.
- As reviewed November 9, 2026, SignalEDI's status notice identifies a pause in production outbound X12 810 invoices, 855 order acknowledgments and 856 shipping notices. Sandbox tests and inbound documents are unaffected by that pause. This is a scoped SignalEDI delivery restriction, not a statement that all Mirakl APIs or integrations are paused. Check current status before planning production delivery.
Questions to resolve from the current buyer packet
- Start with one named marketplace and store. Obtain current operator instructions and documentation available to the approved account. Write down the expected order lifecycle and explicitly exclude features outside the first release, such as returns or catalog enrichment.
- Agree system ownership before mapping fields. Decide where product content, stock, prices, order status and shipment data originate. Define conflict handling so older marketplace imports cannot silently overwrite newer warehouse or ERP decisions.
- Prepare representative, non-sensitive test records for ordinary and exceptional flows. Include multiple lines, partial shipment, an unavailable item, rejected catalog content and repeated updates. Confirm expected outcomes with the implementation owner rather than treating generic examples as certification requirements.
- Design controls around observable outcomes. Record correlation identifiers, sanitized diagnostics and retry history; define reconciliation after interruptions. An HTTP response, file receipt or queue entry alone does not prove that the intended business state is correct.
- Where a separate X12 interface is required, distinguish a 997 functional acknowledgment from business acceptance. It reports syntactic acknowledgment of the exchange, not order approval, successful fulfillment or payment. Agree any required business response and reconciliation evidence separately.
- Before activation, review access scope, volume expectations, recovery procedures and support ownership. Retain the approved mapping and test evidence. Local success does not establish production readiness, marketplace approval or a guaranteed launch date; check SignalEDI's current delivery status.
How SignalEDI handles it
- Prepare a versioned mapping and testing checklist from the requirements you provide.
- Validate synthetic or scrubbed samples before partner testing.
- Review acknowledgement and exception handling before production cutover. Scope is confirmed during setup.
Review mapping and validation in the self-serve workspace before partner testing. Developer quickstart
Pricing
SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.
Compare current plansPractice the workflow before partner testing
These are recommended preparation exercises, not additional partner requirements or a customer success story. Use synthetic or scrubbed samples and adapt each exercise to the current guide assigned to your program.
Advisory: product and offer identity
Use approved test data to map one product and its offer, then submit an invalid attribute and a corrected version through the selected interface.
What a useful result looks like
The team distinguishes product from offer identifiers, observes the rejection and verifies the corrected result without creating duplicates.
Advisory: stock update recovery
Plan a controlled interruption between stock changes, then resume with a repeated update and an older value arriving later.
What a useful result looks like
Agreed ownership and ordering rules prevent stale stock from silently replacing the intended quantity; reconciliation identifies remaining differences.
Advisory: order and partial shipment
Trace a multi-line test order through the agreed acceptance flow and a permitted partial shipment, retaining line references and tracking details.
What a useful result looks like
Quantities and statuses match the agreed outcome, and remaining lines stay distinguishable from shipped or canceled quantities.
Advisory: duplicate processing and evidence
Repeat a processed test order or shipment update, then compare local records with destination state and sanitized diagnostics.
What a useful result looks like
Agreed duplicate handling avoids unintended extra fulfillment and provides evidence to investigate failures without exposing customer data.
Common integration questions
- Can I keep my existing ERP or accounting system?
- Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
- Does validation mean my partner has approved production?
- No. Passing document validation checks your sample against the configured rules. Partner certification, enrollment, transport approval, and permission to send live documents are separate steps controlled by the applicable partner program. Use synthetic or scrubbed samples while preparing and keep the approval evidence before switching to production.
- Where can I see SignalEDI pricing?
- SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.
Authoritative sources
Source review date: 2026-11-09. Links below establish only the facts described; your current buyer-issued materials remain authoritative for program-specific technical requirements.
- Mirakl Connect developer overview — Mirakl
Supports: Connect API coverage for products, inventories, orders and shipments across stores.
- Mirakl Platform developer overview — Mirakl
Supports: Seller, operator and front API roles; platform webhooks and cloud events are restricted to operator users.
- Mirakl Connect product overview — Mirakl
Supports: Mirakl's stated connectivity offering, not evidence of SignalEDI certification or a live connector.
- SignalEDI service status — SignalEDI
Supports: Production outbound X12 810, 855 and 856 pause; sandbox tests and inbound documents unaffected. Recheck current status before activation.
Mirakl questions
- Does Mirakl require X12 EDI for every marketplace integration?
- Do not assume a universal X12 requirement. Mirakl documents APIs and other connectivity options, while each marketplace and connected system determines the workflow. Identify the operator, account role and approved interface first. If your ERP requires EDI, scope its mappings separately; an API order is not automatically an 850, and a shipment update is not automatically an 856.
- Is the SignalEDI Mirakl connector certified or ready for production?
- This guide does not establish a certified connector or production-ready connection. Confirm implementation scope, available operations, access requirements and test evidence with SignalEDI before committing to rollout. Marketplace approval is separate from publishing a guide. Require evidence for the actual store and workflow, and review the current SignalEDI status notice for affected production outbound X12 delivery.
- What should we test before connecting Mirakl to an ERP or warehouse?
- Start with identifier mapping, offer and stock updates, order-state handling and shipment reconciliation. Then exercise rejected data, repeated processing, partial fulfillment and interrupted connectivity. The scenarios below are advisory planning checks, not Mirakl's official certification suite. Your marketplace's current instructions and the agreed project scope determine final acceptance criteria.
Related EDI resources
- Customer requires EDI guide turns the buyer packet into a scoped implementation checklist.
- QuickBooks EDI integration explains supported accounting workflows. Confirm system edition and document scope; it does not establish a connector for this program.
- Managed EDI onboarding is an optional paid path when your team wants help coordinating the scoped partner workflow.
- Walmart EDI requirements covers publicly documented supplier interfaces and buyer-packet boundaries for Walmart programs.
- EDI requirements checker drafts a local readiness checklist without saving buyer data.
Prepare your side for partner testing
SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.
Connect nowTopics: Mirakl integration · Mirakl marketplace integration · Mirakl API integration · Mirakl ERP integration