To start and identify an interchange of zero or more functional groups and interchange-related control segments
Beyond Meat X12 990 Response to a Load Tender
X12 990 (Response to a Load Tender) is the EDI transaction exchanged between Beyond Meat (Beyond Meat (via Manhattan Associates)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 7
- Loops
- 0
- X12 990
- All partners ↗
Transaction context
Where 990 Response to a Load Tender fits on Beyond Meat (via Manhattan Associates)
On Beyond Meat (via Manhattan Associates), the X12 990 Response to a Load Tender follows the 204 Motor Carrier Load Tender and precedes the 214 Transportation Carrier Shipment Status Message and 210 Motor Carrier Freight Details And Invoice in the Logistics cycle.
- Beyond Meat channels
- 1 of 1
- Trading partners
- 168
- Channels
- 240
1 of Beyond Meat's 1 channel carries 990
partners across the Stacksync network trade 990
channels network-wide carry 990
Most common alongside 990
On Manhattan Associates, 990 runs on 17 channels.
The 990 is a motor carrier's formal answer to a 204 load tender, indicating whether it will pick up the offered shipment: accepted, declined, or accepted with conditions. Shippers and brokers require it to confirm capacity electronically instead of by phone, keep routing guides moving, and track carrier tender-acceptance performance. Its B1 segment echoes the shipment identification number from the 204 along with the carrier's SCAC and response code so the reply can be matched to the tender. Sent by the motor carrier, generally in full-truckload workflows, to the shipper, broker, or 3PL that tendered the load on a 204.
When it fires: A shipper or broker tenders a truckload shipment to a carrier on a 204 and the carrier's dispatch decides to take or refuse the load.
Common 990 rejection causes
- A shipment identification number in the B1 segment that does not match the 204, so the shipper's TMS cannot link the response to the tender.
- Reservation action codes outside the partner's accepted set: the base X12 spec defines A (accepted) and D (cancelled), while partner guides add conditional and decline variants, and mismatched code lists cause rejects.
- Missing or incorrect SCAC in the B1 segment, preventing carrier identification.
- Responses sent after the shipper's tender expiration window, by which time the load has already been re-tendered to the next carrier in the routing guide.
Specification summary
X12 990 Response to a Load Tender at the element level
The X12 990 specification defines 16 segments carrying 108 data elements, 38 of which are mandatory.
- Segments
- 16
- Data elements
- 108
- Mandatory elements
- 38
| Segment | Elements | Mandatory |
|---|---|---|
| B1 | 4 | 1 |
| N9 | 3 | 1 |
| N7 | 24 | 1 |
| L9 | 2 | 2 |
| V9 | 20 | 1 |
| K1 | 2 | 1 |
| S5 | 11 | 2 |
Key identifiers in 990
- Shipment Identification Number
- Reference Identification Qualifier
- Equipment Number
- Special Charge or Allowance Code
- Monetary Amount
- Event Code
- Free-Form Message
- Stop Sequence Number
Full segment guideline — 7 segments 0 loops · X12 990 Response to a Load Tender
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit identifying numbers, dates, and other basic data relating to the transaction set
To transmit identifying information as specified by the Reference Identification Qualifier
To transmit information in a free-form format for comment or special instruction
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Trading partners
3+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
MO Motor Carrier Load Tender MO Motor Carrier Freight Details And Invoice TR Transportation Carrier Shipment Status Message
No trading partner matches your search.
Browse the full directory
Beyond Meat Beyond Meat (via Manhattan Associates) EDI 990 FAQ
Common questions about 990 Response to a Load Tender on the Beyond Meat (via Manhattan Associates) channel.
What is X12 990 Response to a Load Tender?
X12 990 (Response to a Load Tender) is the EDI transaction set used to exchange response to a load tender data. Beyond Meat's Beyond Meat (via Manhattan Associates) channel requires it from trading partners.
Does Beyond Meat Beyond Meat (via Manhattan Associates) require 990 for trading partners?
Yes, Beyond Meat (Beyond Meat (via Manhattan Associates)) supports X12 990 Response to a Load Tender. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Beyond Meat 990 with Stacksync?
Most companies go live with Beyond Meat 990 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 990 on Beyond Meat (via Manhattan Associates)?
On Beyond Meat (via Manhattan Associates), X12 990 is typically exchanged alongside 204 Motor Carrier Load Tender, 214 Transportation Carrier Shipment Status Message, 210 Motor Carrier Freight Details And Invoice. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Beyond Meat EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
