NEXCOM (Navy Exchange Service Command) EDI 754 Routing Instructions

Schema Reference

15 segments · X12 754 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

BGN07 Transaction Type Code

O ID 2-2

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: 5

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

LX Loop Repeat: 9,999

LX01 Assigned Number

M N0 1-6

L1101 Reference Identification

C AN 1-50

L1102 Reference Identification Qualifier

C ID 2-3

L1103 Description

C AN 1-80

BLR01 Standard Carrier Alpha Code

M ID 2-4

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

N1 Loop Repeat: 5

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

N201 Name

M AN 1-60

N202 Name

O AN 1-60

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

C ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

C ID 2-3

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 754

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

Validate

Transform

Route

Monitor

Stacksync receives NEXCOM (Navy Exchange Service Command) 754 Routing Instructions and updates your shipping workflow with the assigned carrier, pickup window, and delivery requirements — so your warehouse team has everything they need.

Business unit variations

NEXCOM Test (via SPS Commerce)

NEXCOM (Navy Exchange Service Command) EDI 754 FAQ

Common questions about 754 Routing Instructions transactions with NEXCOM (Navy Exchange Service Command).

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

Most suppliers are fully connected and processing live NEXCOM (Navy Exchange Service Command) EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with NEXCOM (Navy Exchange Service Command)?

No. Stacksync handles the entire EDI transport layer. We connect directly to NEXCOM (Navy Exchange Service Command)'s trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with NEXCOM (Navy Exchange Service Command) compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for NEXCOM (Navy Exchange Service Command)?

Stacksync supports all EDI document types required by NEXCOM (Navy Exchange Service Command) — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect NEXCOM (Navy Exchange Service Command) EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between NEXCOM (Navy Exchange Service Command)'s EDI network and your system in real time.

What happens when NEXCOM (Navy Exchange Service Command) updates their EDI specifications?

Stacksync monitors NEXCOM (Navy Exchange Service Command)'s EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.