Send a retailer a combined 857
Some retailers want one document per shipment that both says what shipped and bills for it: the ship notice and invoice (857). Turn on Combined 857 for such a retailer and SKU.io sends it one 857 per shipment, and no ship notice (856) or invoice (810) at all. Every other retailer keeps its 856 and 810.
The 857 file layout is not confirmed with SPS Commerce. Until SPS Commerce provides the retailer's real 857 layout, don't turn Combined 857 on for a live retailer. The Invoicing by trading partner card shows the same warning while any retailer has it on. The first real files may need changes in SKU.io before they work.
Before you begin
- Connect SPS Commerce. The retailer appears in the settings after its first purchase order arrives, or once you add it by ID under Flow by retailer.
- Each 857 carries exactly one shipment and one invoice. Invoice each shipment on its own, with freight on that invoice.
Turn on the 857
- Go to Apps & Integrations, search for SPS, and choose SPS Commerce.
- Open your connection, then click Settings.
- Scroll to the Invoicing by trading partner card.
- Find the retailer, and turn on Combined 857.
- Click Save Changes.
Turning it on sets three of the retailer's other settings and locks them, because an 857 needs them that way:
| Setting | Set to | Why |
|---|---|---|
| Ship notices (856) sent by | SKU.io | The 857 is the retailer's ship notice, so SKU.io has to send it |
| Freight | On each shipment invoice | An 857 bills one shipment with one invoice, so a separate freight invoice would never reach the retailer |
| Credit memos (810 CR) | Off | The retailer gets no 810, so no credit memo can go as one |
Hover over a locked setting to read why. To change one, turn Combined 857 off first.
Settings that can't go with the 857
Saving is refused, with a message that names the retailer, when the 857 meets one of these:
| Combination | Message starts |
|---|---|
| The retailer is on Receive only, as its flow or for any warehouse | On receive only, the 3PL sends …'s ship notice and SKU.io sends only the 810, so it can't take an 857 from SKU.io. |
| The retailer has the UPS: one 856 per carton document rule | An 857 reports the whole shipment in one document, so it can't go one per UPS carton for …. |
| Ship notices (856) sent by is An outside 3PL | An 857 is the retailer's ship notice, so SKU.io has to send it. |
| Freight is On a separate invoice | An 857 bills one shipment with one invoice, so a separate freight invoice would never reach …. |
| Credit memos (810 CR) is on | A retailer on the 857 gets no 810, so credit memos can't go to … as an 810. |
Each message ends by saying to change that setting, or turn the 857 off.
The retailer's other document rules, its ship notice structure, carton detail and its one-order-per-distribution-center split all still apply. They shape the ship notice part of the 857 the way they would shape an 856.
What happens when a shipment ships
When the shipment is recorded, and packed if the retailer needs cartons, SKU.io sends the 857:
- For an order invoiced as a whole, the 857 bills what shipped at the purchase order's prices.
- For an order invoiced per shipment, the 857 waits until the shipment's invoice is issued, then carries that invoice.
The Documents tab lists it as Ship notice and invoice (857). On the shipment's Cartons tab, the last step reads Ship notice and invoice (857) instead of separate ship notice and invoice steps. On a per-shipment invoice, the EDI tab is titled EDI 857 ship notice and invoice, with Regenerate and Send 857.
What happens to shipments when you switch
- A ship notice or invoice that hasn't gone yet gives way to the 857. SKU.io withdraws it and sends the 857 instead.
- A shipment whose 856 or 810 already went gets no 857, because that would report it twice. It's held with: This shipment's … went out before the retailer moved to the 857, so SKU.io won't send an 857 and report it twice. Sort out what's left of this shipment with the retailer.
- An 856 or 810 that tries to go later, for example from a retry, is stopped. It shows Failed on the Documents tab with This … was not sent, because this retailer takes one 857 per shipment instead of an 856 and an 810., can't be resent, and raises an alert titled 856 held back: this retailer takes an 857 or 810 held back: this retailer takes an 857.
- When you turn the 857 off, shipments that already have an 857 keep it, and get no 856 or 810 on top. Shipments still on hold get an 856 and 810 only when someone asks for them, with Submit Now on the shipment.
When an 857 is held
SKU.io holds an 857 rather than send one that doesn't match the shipment. The reason shows on the shipment's Cartons tab and on the invoice's EDI tab. The ones that need you also raise an alert titled Ship notice and invoice (857) is on hold.
| Reason starts | What to do |
|---|---|
| This shipment is on … invoices, and an 857 carries one. | Void the extra invoices so one bills the whole shipment |
| Invoice … bills more than one shipment, and an 857 is one shipment and one invoice. | Void it, and invoice each shipment on its own |
| Invoice … doesn't bill the quantities this shipment shipped, and an 857 states both. | Void it, and invoice the shipment as shipped |
| This shipment is marked not to be invoiced, and an 857 can't go without an invoice… | Create its invoice, or tell the retailer another way |
| This shipment's ship notice and invoice (857) waits for its invoice. | Nothing. It goes when the invoice is issued |
| This warehouse is on receive only… or The 3PL sends this retailer's ship notices… | Choose another flow for that warehouse, or set who sends ship notices, or turn the 857 off |
A ship notice rule, such as waiting for the carrier pickup, holds the 857 the same way it holds an 856, with the Ship notice held alert. See Set a retailer's document rules.
Other 857 alerts
| Alert title | What to do |
|---|---|
| Ship notice and invoice (857) could not be sent | Fix the cause in the message, then click Resend on the Documents tab, or Submit Now on the shipment |
| Ship notice and invoice (857) was rejected | The shipment is neither reported nor billed. Correct the shipment or its invoice, then click Resend. SKU.io writes the 857 again from how they stand then |
| Voided invoice is on a sent 857 | SKU.io can't withdraw an 857 that went. Tell the retailer the invoice no longer stands |
| Voided invoice is on an 857 being sent | Check the Documents tab. If the 857 shows Sent, tell the retailer the invoice no longer stands |
| Voided invoice has a sent 810 | The invoice's 810 went before the retailer moved to the 857, and SKU.io sends it no more 810s. Tell the retailer the invoice no longer stands |
| Invoice can't go on an 857 | The invoice bills no shipment, or its shipment's 857 already carries another invoice. Send it to the retailer another way |
There's no cancelling 857. To correct one the retailer accepted, contact the retailer.