AIMS360 runs Altar'd State EDI natively inside the ERP: 850 stand-alone and cross-dock purchase orders linked correctly to their bulk order, line-level 855 acknowledgments, 856 ASNs with GS1-128 labels and 810 invoices from one master stock record.
Altar'd State EDI Integration
AIMS360 is a consumer brands ERP with Altar'd State EDI built in. One platform manages your style, color and size inventory and exchanges every document Altar'd State requires: 850 purchase orders in, with cross-dock releases linked to the bulk order they belong to, 855 acknowledgments with full line detail, 856 ASNs with GS1-128 labels, and 810 invoices out. No separate EDI provider, and the connection is fully managed by our EDI team.
What does it take to trade EDI with Altar'd State? Altar'd State is the women's fashion, accessories and gift retailer owned by Stand Out For Good, Inc. Its EDI program runs on the 850 purchase order in, the 856 ASN and 810 invoice out, plus an 855 acknowledgment that should always carry line item detail. What separates this trading partner from most others is the purchase order structure: Altar'd State issues stand-alone orders typed SA and cross-dock orders typed KN, and a KN order is a release against a bulk commitment rather than new demand. Handle it as new demand and you have double counted your own inventory. AIMS360 links each release to its bulk order so the order book stays honest, and runs the whole flow from one system.
The Mechanic That Matters
Altar'd State sends purchase orders under two types, and they need to be processed differently. This is the single most common onboarding mistake on this account.
In practice this can represent a blanket or bulk commitment, the large up-front buy the retailer will draw against over time. Processed as a bulk order, it holds the total commitment in your order book without pretending it all ships at once.
A release or distribution order. It is not new business, it is a portion of the bulk commitment being called forward for specific stores or a distribution center. It has to be linked to the bulk order it draws from, so the release consumes the commitment rather than adding to it.
Treat every KN release as a fresh order and your open order book inflates. The same units get committed twice, availability looks worse than it is, and you either turn away business you could have taken or promise units already spoken for. It surfaces weeks later as a fill rate problem nobody can explain.
Goods move across the dock into store-level shipments instead of resting in the retailer's warehouse. Efficient for them, demanding for you: shipments are smaller, more frequent and store-routed, and the ASN has to be right every time because there is no buffer stage to catch an error.
Altar'd State EDI Documents
Altar'd State uses the ANSI ASC X12 standard and has expanded its document set over time. Each document is created from the same ERP records that run your inventory, warehouse and accounting.
| Transaction | What it does for Altar'd State |
|---|---|
| EDI 850 purchase order | Sent as type SA or KN. AIMS360 holds SA as the bulk commitment and links each KN release to it, validated against live inventory. |
| EDI 855 acknowledgment | Line item detail always included, with order-level and line-level status codes sent from the order record. |
| EDI 856 ship notice (ASN) | Store-routed, carton-level shipment notice with GS1-128 labels, transmitted at shipment close. |
| EDI 810 invoice | Bills Altar'd State electronically, with the order, shipment and terms already attached. |
| EDI 860 / 997 | Purchase order change and functional acknowledgment, phased into the program over time. Confirm current status against your guidelines. |
Order types, trading partner codes and program scope come from the vendor guidelines Altar'd State issues to you and can change. Confirm current requirements with your buyer or their EDI department before onboarding.
The 855 Acknowledgment
An 855 is expected for each 850, and line item detail should always be included. That gives you room most trading partners do not.
| Level | Code and meaning |
|---|---|
| Order | AC acknowledge with detail and change · AK acknowledge with no detail or change · RJ rejected, no detail |
| Line | IA item accepted · IB item backordered · IR item rejected · IQ accepted, quantity changed · IP accepted, price changed · DR accepted, date rescheduled |
Where a retailer accepts order-level status only, the answer is all or nothing. Here you can accept most of an order, flag one style as backordered, revise a quantity on another and reschedule a third, all in one document. That protects the relationship.
Six line-level codes are only useful if the acknowledgment is generated from real availability rather than assembled by hand. In AIMS360 the 850 lands against live stock, so the line-level answer is accurate the moment it goes back.
The Brand Family
Stand Out For Good, Inc. is the parent company behind Altar'd State and its sister brands. Which of them your agreement covers is a vendor agreement question rather than an assumption.
The core women's fashion banner, boho-leaning apparel, accessories and gift, with a store experience built around the giving-back mission the group is known for.
Mid and plus size fashion for sizes 10 to 24, formerly A'Beautiful Soul. Deeper size ranges mean a different size curve and a different buy from the core banner.
Bridal and wedding, with the longer lead times and made-to-order rhythm bridal brings compared with seasonal fashion.
Children's, which adds its own safety documentation expectations on top of standard vendor requirements.
A further banner in the group. Assortment and program scope differ, so confirm coverage rather than assuming a shared setup.
Whichever banners you supply, AIMS360 keeps them on one inventory pool with channel rules, so bulk commitments, releases and your DTC channel cannot promise the same units twice.
How Altar'd State EDI Works
AIMS360 sits between Altar'd State and your warehouse, turning each EDI document into action and each action back into the compliant document Altar'd State expects.
| Step | What happens |
|---|---|
| 1. 850 SA bulk order received | Altar'd State transmits a stand-alone purchase order. AIMS360 holds it as the bulk commitment in the order book against live inventory. |
| 2. 850 KN release linked to the bulk | Each cross-dock release is linked to the bulk order it draws from, so it consumes the commitment rather than adding new demand. |
| 3. 855 sent with line detail | Acceptance, backorders, quantity, price and date changes go back line by line from the order record. |
| 4. Pick, pack, ship in the built-in WMS | Store-routed shipments built to packing rules with GS1-128 carton labels. |
| 5. 856 ASN at shipment close | Transmits per store-routed shipment, derived from the same carton record as the labels. |
| 6. 810 invoice | Accounting invoices Altar'd State automatically with the order, shipment and terms attached. |
Managed Altar'd State Onboarding
Your buyer or the Altar'd State EDI department issues the vendor number, guidelines and routing requirements. AIMS360's EDI specialists configure the customer and trading partner records, load the store to DC cross reference, set SCAC codes per carrier and packing rules per trading partner, then test the part that matters most: a bulk order processed, a release linked against it, and the order book checked to confirm the commitment was consumed rather than doubled. That is the same fully managed EDI service behind every retailer we support. Get the bulk and release flow right and the rest is routine.
Altar'd State EDI FAQ
Altar'd State EDI is the electronic data interchange link a vendor runs to trade purchase orders, ship notices and invoices with Altar'd State, the women's fashion retailer owned by Stand Out For Good, Inc. The working set is the 850 purchase order in, the 856 ASN and 810 invoice out, plus an 855 acknowledgment. Cartons need GS1-128 labels, and the trading partner issues two purchase order types that have to be handled differently.
Altar'd State sends purchase orders typed SA for stand alone or KN for cross-dock. An SA order can represent a bulk commitment. A KN order is a release against that bulk and has to be linked to it. Processing a release as new demand double counts inventory that was already committed by the bulk.
On a cross-dock program the retailer places a bulk commitment up front, then releases portions to specific stores or distribution centers as needed. Goods move across the dock into store-level shipments rather than resting in the retailer's warehouse. The vendor's system has to hold the bulk order and draw each release against it.
The working set is the 850, 856 and 810, with an 855 acknowledgment. Altar'd State has moved toward 860 changes and 997 acknowledgments over time, so confirm the exact required set against the current vendor guidelines issued to you.
Line item detail should always be included. Order level: AC acknowledge with detail and change, AK acknowledge with no detail or change, RJ rejected. Line level: IA item accepted, IB backordered, IR rejected, IQ accepted with quantity change, IP accepted with price change, DR accepted with date rescheduled.
It is far more expressive than a simple accept or reject. Altar'd State expects line detail and gives you six line-level codes, so you can accept most of an order while flagging one style as backordered, another with a revised quantity and another with a new date, provided the acknowledgment is generated from live inventory.
Stand Out For Good, Inc. is the parent company behind Altar'd State, Arula, Vow'd Weddings, Tullabee and AS Revival. Program scope is defined by your vendor agreement rather than the parent company. AIMS360 configures each trading partner relationship your agreement specifies while keeping every banner on one stock record.
No. AIMS360 includes managed EDI as part of the platform, with no separate EDI vendor, no per-document fees and no middleware layer to reconcile.
Typically a few weeks once your vendor number and guidelines are issued. The bulk and release structure is the part worth testing hardest, because it is where demand can be double counted if releases are not linked to their bulk order.
Get Started
Bring your Altar'd State program to a demo and we will walk through the SA and KN order structure, the line-level 855, store-routed shipments, and how managed onboarding gets you compliant from the first release.
