Skip to main content

Your retailer runs on Radial. Get your side ready for onboarding.

Bring your retailer packet and deadline. Prepare mappings and safe samples for partner testing, with connection scope and availability confirmed during setup.

Quick answers

Can SignalEDI help me connect to Radial?
SignalEDI helps prepare mappings, sample validation, and the workflow required for your Radial 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 Radial 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 Radial?
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.
Review integration scope

Plan the integration workflow

SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.

  1. 1. Your business system

    Identify the source records, system edition, data owner, and allowed access.

  2. 2. SignalEDI preparation

    Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.

  3. 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 checklist

Download the onboarding worksheet (text)

What does your Radial connection need to exchange?

The Exchange documents 850, 856, 810 and 846 for its Radial program. Your retailer's packet controls your required documents, versions, directions and deadlines.

850 Purchase Order: orders ready to work

Preserve order and line references, items, quantities and delivery details in your business workflow.

856 Ship Notice: shipment detail connected

Align carton, carrier and tracking details with fulfillment. Follow the retailer's submission window.

810 Invoice: references that reconcile

Link orders and fulfilled quantities. Confirm invoice grouping, totals and correction rules.

846 Inventory: availability kept current

Confirm stock source, allocations, update schedule and handling of stale or rejected records.

855 Order Acknowledgment: when assigned

When required, confirm how the retailer represents accepted, rejected and changed lines.

997 Functional Acknowledgment: syntax feedback

When assigned, track syntax feedback separately from business acceptance, shipment and payment.

How does getting connected work?

1. Bring the retailer and deadline

Gather the current packet and named program. Confirm the assigned browser or system-to-system route before selecting it.

2. Confirm your business-system path

Identify your software edition and source records. Check connector availability, supported operations and add-on terms before choosing an ERP, file or API approach.

3. Map, validate and test

Resolve mapping errors with safe samples. Retailer testing, certification and approval remain separate from trial or simulator success.

4. Review the production decision

Confirm partner sign-off, service status and go-live permission. Assign exception owners. The outbound pause must end before affected production documents can flow.

Who is this for?

Suppliers with a retailer-issued Radial packet, including:

  • A first mandate without an EDI team.
  • Growing volume that burdens permitted portal entry.
  • Another retailer requiring separate mapping and approval.
  • Provider comparisons using volume, partner count and total cost.

What does it cost?

Compare Starter and Growth using document volume, partner count, overages and connector scope. Evaluation is separate from production approval; paid add-ons are excluded from the core-plan trial.

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 charges

Have a retailer packet? Start with the requirements.

Start an evaluation or email your questions. Confirm scope and approvals before committing to a live date.

SignalEDI is an independent EDI and API integration provider, not endorsed by Radial. This page is not evidence of a commercial partnership, certification or an active production connection.

Public sources reviewed 2026-11-09

What the public record confirms

  • The Exchange's published dropship guide identifies Radial Drop Ship Manager (VendorNet) and an 850, 856, 810 and 846 workflow. This is evidence for the Exchange program, not a transaction matrix or retailer roster applicable to every Radial supplier.
  • Radial's non-Radial fulfillment feeds do not apply to its Dropship product integration. Use the guide assigned to your product and retailer.
  • X12 defines the 997 as syntax-analysis feedback, not semantic business acceptance. A technical acknowledgment cannot establish that an order was accepted, goods shipped or an invoice will be paid.
  • SignalEDI's status page reports a production-delivery pause for outbound 810, 855 and 856 documents, reviewed November 9, 2026. Sandbox tests and inbound documents are unaffected. This independent guide establishes no Radial endorsement, certification or active connection.

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.

  • 850 purchase orders: documented for the Exchange dropship program; confirm your retailer's version, identifiers and line mapping. document guide →
  • 856 shipment notices: confirm packing, carrier, tracking, partial fulfillment and the retailer-specific submission window. document guide →
  • 810 invoices: confirm order references, quantities, totals and corrections against the assigned billing instructions. document guide →
  • 846 inventory: confirm whether required, its stock definition, update cadence and stale-record handling. document guide →
  • 855 order acknowledgments: include only when assigned by the retailer; not verified as a universal Radial requirement. document guide →
  • 997 functional acknowledgments: confirm applicability and direction; syntax acceptance does not establish business, shipment or payment acceptance. document guide →

Connectivity and testing requirements

Connectivity

Confirm whether the current Radial 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.

  • The Exchange's published dropship guide identifies Radial Drop Ship Manager (VendorNet) and an 850, 856, 810 and 846 workflow. This is evidence for the Exchange program, not a transaction matrix or retailer roster applicable to every Radial supplier.
  • Radial's non-Radial fulfillment feeds do not apply to its Dropship product integration. Use the guide assigned to your product and retailer.
  • X12 defines the 997 as syntax-analysis feedback, not semantic business acceptance. A technical acknowledgment cannot establish that an order was accepted, goods shipped or an invoice will be paid.
  • SignalEDI's status page reports a production-delivery pause for outbound 810, 855 and 856 documents, reviewed November 9, 2026. Sandbox tests and inbound documents are unaffected. This independent guide establishes no Radial endorsement, certification or active connection.

Questions to resolve from the current buyer packet

  • Identify the retailer, Radial product and named program. Confirm the assigned browser or system-to-system route; portal availability does not waive an EDI mandate.
  • Obtain the current order, shipment, inventory and cancellation scope; record formats and versions.
  • Confirm connector scope and software edition. Reconcile item, order, quantity, tracking and carrier mappings with their owners.
  • Test partial shipments, retries, duplicate messages, rejected records and corrections using safe samples.
  • Keep test and production evidence separate. Confirm retailer approval and current platform status before live exchange; do not schedule affected documents around an unresolved delivery pause.

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 plans

Practice 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.

Identify product and retailer scope

Advisory exercise: compare the retailer packet's named Radial product with the assigned guide. Record the requested order, shipment, inventory and cancellation scope, then deliberately introduce a ROM feed example into a Dropship scenario to test whether the mismatch is noticed.

What a useful result looks like

The proposed pass condition is a named guide revision for each workflow. A ROM example cannot silently become a Dropship implementation. Questions stay tied to the assigned retailer rather than becoming universal requirements.

Preserve order-line identity

Advisory exercise: prepare a synthetic multi-line order with repeated items and partial fulfillment. Trace order, line, quantity, units, carrier and tracking through the mapping. Compare the field names and grouping with the assigned specification before considering the sample ready.

What a useful result looks like

The proposed pass condition is that shipments reconcile to the correct order lines without relying on SKU alone. Partial fulfillment cannot close the whole order, and ambiguous identifiers remain visible for correction.

Exercise retries and corrections

Advisory exercise: simulate a rejected record and an uncertain transmission outcome. Use the assigned response rules to determine what evidence is needed before retrying, then introduce delayed feedback to check that a correction remains distinguishable from a duplicate.

What a useful result looks like

The proposed pass condition is an intact business reference and attempt history. Uncertain requests are checked before resending. Transport success and syntax acceptance remain distinct from a completed business transaction or retailer approval.

Keep test and production evidence distinct

Advisory exercise: identify the endpoint, account and retailer for each sample. Compare completed tests with outstanding approvals and current platform status. Include an affected outbound document to verify that the production pause remains a visible cutover dependency.

What a useful result looks like

The proposed pass condition is a readiness statement separating tested behavior from production permission. Sandbox success cannot override a pause or missing approval. No local artifact becomes evidence of Radial certification or an active connection.

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.

Radial questions

Are Radial Dropship and Radial Order Management integrations the same?
No. Radial’s non-Radial fulfillment feeds do not apply to its Dropship product integration. Confirm the product and retailer named in your packet before selecting a guide.
Can a Radial browser portal replace the EDI requirement in my retailer's packet?
No automatic waiver applies. The Exchange's browser option does not establish another retailer's permissions. Confirm your assigned route, required documents, responses and shipment windows in the current account instructions before selecting a portal.
Can SignalEDI promise my Radial connection will be live by a fixed date?
No. Scope, source-system readiness, retailer testing and final approval determine timing. SignalEDI's current status also reports an outbound production pause for 810, 855 and 856. Check the status link and confirm the actual connector before setting a date. This page establishes neither Radial certification nor an approved production connection.

Related EDI resources

Prepare your side for partner testing

SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.

Connect now

Topics: Radial EDI · Radial supplier onboarding · Radial EDI requirements

© 2026 SignalEDI Inc. All rights reserved.