X12

Outbound

NEXCOM (Navy Exchange Service Command) X12 753 Request for Routing Instructions

NEXCOM Trans

The EDI 753 is sent by suppliers to request shipping routing instructions from NEXCOM (Navy Exchange Service Command). It identifies the shipment ready for pickup and asks the retailer to provide carrier assignment and delivery scheduling.

14segments

2loops

9mandatory

Book a demo

← All NEXCOM (Navy Exchange Service Command) transactions

Schema Reference

14 segments · X12 753 Request for Routing Instructions

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

BGN01 Transaction Set Purpose Code

M ID 2-2

BGN02 Reference Identification

M AN 1-50

BGN03 Date

M DT 8-8

BGN04 Time

C TM 4-8

PER01 Contact Function Code

M ID 2-2

PER02 Name

O AN 1-60

PER03 Communication Number Qualifier

C ID 2-2

PER04 Communication Number

C AN 1-256

N1 Loop Repeat: 1

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

LX01 Assigned Number

M N0 1-6

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

L1101 Reference Identification

C AN 1-50

L1102 Reference Identification Qualifier

C ID 2-3

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

G6203 Time Qualifier

C ID 1-2

G6204 Time

C TM 4-8

USI01 Quantity

M R 1-15

USI02 Packaging Form Code

M ID 3-3

USI03 Yes/No Condition or Response Code

O ID 1-1

OID Loop

OID01 Reference Identification

C AN 1-50

OID02 Purchase Order Number

C AN 1-22

OID03 Reference Identification

O AN 1-50

OID04 Packaging Form Code

C ID 3-3

OID05 Quantity

C R 1-15

OID06 Weight Unit Code

C ID 1-1

OID07 Weight

C R 1-10

OID08 Volume Unit Qualifier

C ID 1-1

OID09 Volume

C R 1-8

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

How It Works

Automating NEXCOM (Navy Exchange Service Command) EDI 753

Stacksync validates, transforms, and delivers your 753 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate

Transform

Route

Monitor

Stacksync sends 753 Routing Requests to NEXCOM (Navy Exchange Service Command) automatically when your warehouse marks an order ready to ship — triggering carrier assignment without phone calls or portal logins.

Business unit variations

NEXCOM Test (via SPS Commerce)

NEXCOM (Navy Exchange Service Command) EDI 753 FAQ

Common questions about 753 Request for Routing Instructions transactions with NEXCOM (Navy Exchange Service Command).

What is a NEXCOM (Navy Exchange Service Command) EDI 753 Request for Routing Instructions?

The NEXCOM (Navy Exchange Service Command) EDI 753 Request for Routing Instructions is an X12 transaction set used to exchange Request for Routing Instructions data electronically between trading partners. As a outbound document, it standardizes the communication of Request for Routing Instructions information between NEXCOM (Navy Exchange Service Command) and their suppliers, carriers, or partners. Stacksync processes NEXCOM (Navy Exchange Service Command) 753 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with NEXCOM (Navy Exchange Service Command)'s requirements in real time.

How does Stacksync automate NEXCOM (Navy Exchange Service Command) EDI 753 Request for Routing Instructions transactions?

Stacksync handles NEXCOM (Navy Exchange Service Command) EDI 753 Request for Routing Instructions transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For outbound 753 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every NEXCOM (Navy Exchange Service Command) 753 document meets their specific formatting requirements before transmission or after receipt.

What are common NEXCOM (Navy Exchange Service Command) EDI 753 errors and how do I fix them?

Common errors in NEXCOM (Navy Exchange Service Command) EDI 753 Request for Routing Instructions transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates NEXCOM (Navy Exchange Service Command) 753 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

How long does it take to set up NEXCOM (Navy Exchange Service Command) EDI 753 with Stacksync?

Most NEXCOM (Navy Exchange Service Command) EDI 753 Request for Routing Instructions integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between NEXCOM (Navy Exchange Service Command)'s 753 format and your system, running test transactions, and completing NEXCOM (Navy Exchange Service Command)'s certification process if required. Stacksync includes pre-built mappings for NEXCOM (Navy Exchange Service Command)'s most common 753 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize NEXCOM (Navy Exchange Service Command) EDI 753 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how NEXCOM (Navy Exchange Service Command) EDI 753 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If NEXCOM (Navy Exchange Service Command) updates their 753 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate NEXCOM (Navy Exchange Service Command) EDI?