Every error our platform can produce, with what it means and what to do about it.
161 of them, written in English rather than copied out of a specification. No login,
no form.
Most EDI errors are caused by the file a trading partner sent rather than by anything you
did. Where that is the case, it says so — because the first useful thing to know is
usually whose problem it is.
We cannot say what another retailer would cost, so we did not add one.
Pricing comes from the plan on your account, and this account is not on one yet. Rather than adding a retailer at a price nobody can name, and settling the question on an invoice later, we stop.
What to do: Ask us to finish setting the account up. This is our side rather than yours, and it is usually a minute of work.
New connections are paused; your data is untouched.
New connections cannot be created. Your documents remain fully available and exportable — we do not withhold your records.
What to do: You can still read and export everything, so nothing is urgent on your side. Email hello@palletlabs.org and we will tell you exactly what is outstanding and reactivate you.
The memo is for more or less than its own lines add up to.
The header states one amount and the detail lines come to another. Nothing in the document explains the difference.
What to do: Query it before it is settled. This is the strongest possible ground for disputing a deduction, because the sender’s own document disagrees with itself — and it is much easier to raise now than at the year end.
Part of this memo runs the other way from the rest of it.
A line is marked as a credit while the memo as a whole is marked as a debit, or the reverse. That is legal — a memo can net one against the other — but it also means the header total cannot be read as a single direction.
What to do: Check the line amounts individually rather than trusting the header. If the sender did not mean to net them, this is usually a keying error on their side and they will reissue.
Somebody at your company signed this already.
The acceptance is recorded with who accepted it and when.
What to do: Nothing. You can see the record on the Contract page.
There is already a sandbox for that email address.
The demo creates one sandbox per address so a second request does not quietly replace the first and lose whatever you had already sent into it.
What to do: Use the link from the original email. If you cannot find it, ask us and we will resend it rather than start you over.
There is already an open request for this.
A second identical request would not speed anything up and would make our review queue misleading.
What to do: Wait for the existing one, or cancel it first if the details have changed.
Only a signed-in person can accept a charge, and this request was not from one.
Something asked us to add a retailer, which costs money every month, and the request came from an API key rather than from somebody signed in to the portal. A key lives in a config file and gets copied between environments, so it is not evidence that anybody decided to spend money. There is no permission that changes this.
What to do: Add the retailer from the portal, signed in as somebody who holds the "Agree to charges" permission. The account owner has it; anybody else needs it granted. Everything else about trading partners can still be done with an API key.
Your account is not allowed to do that particular thing.
You are signed in and the request was understood — what is missing is one named permission. Accounts start with a role, and individual capabilities are added on top one at a time, so somebody who can print a packing slip may legitimately not be able to see an invoice. The response names the permission that is missing rather than saying only "forbidden", because being told what you lack is the difference between a two-minute fix and an afternoon of asking around.
What to do: Ask whoever administers your Greenbar account to add the named permission. For our own staff accounts, an admin grants it from Settings, Staff.
The price moved while the screen was open, so nothing was added.
You accepted one figure and the current one is different — usually because the plan changed, or because another retailer was added in between and this one is no longer inside your allowance. Nothing was created and nothing was billed.
What to do: Look at the new amount and confirm again if it is still what you want. The refusal carries the current quote so there is nothing to look up.
Adding this retailer costs money, so the amount has to be accepted first.
The request did not say what it expected to pay. We will not take an unspecified yes to a recurring charge, because an unspecified yes is agreement to whatever the price happened to be at that instant.
What to do: The refusal carries the current quote. Send it back as the amount you accept, which is what the portal button does for you.
A row has a different number of columns from the heading.
The values on that row may have been read into the wrong columns. The row is reported rather than guessed at, because a quantity read into a price column is worse than no row at all.
What to do: Open the file at the line named. An unescaped comma inside a description is the usual cause, and the partner can fix it by quoting that column.
Technically: The row had a different field count from the header row.
A quote appears in the middle of a value that was not quoted.
That cell was read as the literal text including the quote. The row still came through, so this is usually cosmetic rather than serious.
What to do: Check the value on the line named. If it should contain a quote mark, nothing needs doing. If the whole cell was meant to be quoted, ask the partner to re-export.
Technically: A double-quote appeared after the first character of an unquoted field.
A quoted value in the spreadsheet is never closed.
Everything after that point reads as one enormous cell, so the rest of the file could not be made sense of. Nothing was lost — the file is stored exactly as it arrived.
What to do: A stray double-quote inside a product description is the usual cause. Ask the partner to re-export the file; most systems quote correctly when asked again.
Technically: A quoted field was opened and the file ended before the closing quote. RFC 4180 requires an embedded quote to be doubled.
The order says how many lines it has, and it has a different number.
The count at the end of the document disagrees with the lines actually in it. That usually means the file was truncated, so lines may be missing — which is why this is said out loud rather than quietly ignored.
What to do: Compare the line count against what the retailer says they sent. If the file is short, ask them to resend; do not fulfil a partial order on the assumption that the missing lines were not important.
Nothing arrived inside it.
Nothing was in it to process. This is almost always a transfer that went wrong rather than anything your trading partner meant to send.
What to do: Ask them to send it again. If empty files keep arriving, their system is probably creating the file before it has anything to write into it.
Technically: No segments were found in the payload.
A section of the file contains no documents.
A group was opened and closed with nothing inside it. Harmless in itself.
What to do: No action needed unless you were expecting a document that has not arrived, in which case ask your partner to check it was actually sent.
Technically: A functional group contained no transaction sets.
The file is correctly formed but contains no documents.
It has an opening and a closing and nothing between them. Nothing was lost, because there was nothing there.
What to do: Usually means their system had nothing to send and produced a file anyway. Worth mentioning only if you were expecting something.
Technically: An interchange contained no functional groups.
The contact form needs a name, a working email address, and a sentence.
One of the three is missing or too short. The message in particular has a minimum, because a two-word enquiry produces something nobody can answer and leaves the sender believing they have told us something.
What to do: The refusal names the field. If the form keeps rejecting an address you know is good, email hello@palletlabs.org and we will pick it up from there.
We could not read the file of shipments, so nothing was sent.
A file answering orders is read whole before anything goes to a retailer, and a row in this one could not be understood: a missing PO number, a quantity that is not a number, or a date we cannot read. Sending the rows we could read would confirm part of a shipment, which is how invoices end up short.
What to do: Each problem is listed with its row. Fix those rows in your export and send the whole file again; orders already sent will not be sent twice.
This is a staff-only area.
Your account is a customer account and this endpoint is for Greenbar staff.
What to do: If you need something from here, ask us. There is nothing behind it that affects your own data.
A section of the file was never closed.
Documents are grouped inside the file, and one of those groups has no end marker. We could not tell where it was meant to stop.
What to do: Ask your partner to resend. Their EDI software is producing a structurally incomplete file, which is worth telling them about.
Technically: A GS opened a functional group with no matching GE.
A section ends without ever having started.
There is a closing marker for a group of documents that was never opened. The file structure is inconsistent.
What to do: Ask your partner to resend. This is a fault in whatever produced the file, not something you can correct at your end.
Technically: A GE segment appeared with no open functional group.
A section claims a different number of documents than it holds.
The count written into the file does not match what we found. We stopped rather than guess which is right, because processing the wrong number of orders is worse than processing none.
What to do: Ask your partner to resend. A repeated, identical mismatch points at their software rather than the transfer.
Technically: GE01 does not equal the number of transaction sets found in the group.
A section opens and closes with different reference numbers.
The two ends of one section disagree, so we cannot be confident everything between them belongs together.
What to do: Ask your partner to resend the file.
Technically: GE02 does not match GS06.
Part of the file sits outside the structure that holds it.
A group of documents appears before the file properly begins. We kept it and recorded the problem rather than discarding anything.
What to do: Ask your partner to resend. Two files appended to each other is the most common cause.
Technically: A GS segment appeared outside any ISA interchange.
That GS1 company prefix is already registered to another account.
GS1 issue each company prefix to exactly one company. Two accounts allocating carton numbers from the same prefix would eventually give the same number to two different pallets, so we will not register it twice.
What to do: Check the prefix against your GS1 certificate — a single wrong digit is the usual cause. If it is right, you probably have a second account with us; tell us and we will join them up rather than having you run two ranges.
Every carton number in your GS1 prefix has been issued.
A company prefix contains a fixed number of serial references and yours are all used. We will not start again at one, because two pallets with the same number is worse than a pallet with none: the second to arrive is either rejected as already received or quietly overwrites the first.
What to do: Ask GS1 for a longer prefix — a shorter company prefix leaves more digits for the serial, so a seven-digit prefix gives a thousand times the range of a ten-digit one. Send us the new one and we will switch to it; everything already issued stays on record.
A traceable product has no GTIN, so its lot code cannot be completed.
A traceability lot code is a GTIN and a lot number together. The lot alone says which production run but not what the product is, so on its own it identifies nothing. This product is marked as traceable and we have no GTIN for it.
What to do: Add the GTIN under Account, Your products. It is the number already printed on your barcode, issued from your GS1 company prefix — not the retailer’s part number, which means something only to them.
The ship notice describes something inside a container that is not there.
A ship notice is a nested structure — shipment, then orders, then cartons, then items — and one level refers to a parent that was never declared. The structure could not be rebuilt, so the notice may be incomplete.
What to do: Ask the partner to resend. This is a bug in whatever builds their file, and worth telling them about rather than working around.
Technically: An HL segment named a parent id with no matching HL.
That address is not somewhere we will connect to.
The host given is on a private or reserved network — a loopback address, an internal range, or a cloud metadata endpoint. Those are addresses inside somebody’s own network rather than a retailer’s server, so a connection to one either reaches nothing or reaches something it should not.
What to do: Check the address against the retailer’s implementation guide; this is almost always a typo or a value copied from an internal test setup. If a retailer genuinely asks us to connect to something unroutable, that needs a conversation rather than a configuration change.
The file ended part-way through.
We received a beginning but never the end, so we cannot be sure we have the whole thing. Rather than risk processing half a document, we stopped. Everything received is stored.
What to do: Ask your partner to send it again. If it keeps happening, something is cutting the transfer short — a timeout or a size limit on their side is the usual cause.
Technically: An ISA opened an interchange with no matching IEA before the end of the file.
The file has an ending with no beginning.
It contains the closing marker of a document whose opening is missing, which usually means two files were joined together incorrectly or the start was trimmed off.
What to do: Ask your partner to resend as a single complete file. If they are batching several documents together, something in that process is dropping a header.
Technically: An IEA segment appeared with no open interchange.
The file disagrees with itself about how much it contains.
It states how many sections it holds, and that number does not match what is actually there. Either something was lost in transit or their software miscounted. We have not processed it, because we cannot tell which.
What to do: Ask your partner to resend. If the same mismatch repeats with the same numbers, it is a bug in their EDI software rather than a transfer problem, and worth reporting to them.
Technically: IEA01 does not equal the number of functional groups found in the interchange.
The reference numbers at the start and end do not match.
Each file carries the same reference at its opening and closing, so a mismatch means the two halves may not belong together — most often two files spliced by mistake.
What to do: Ask your partner to resend. If they batch documents before sending, that process is the place to look.
Technically: IEA02 does not match ISA13.
A pallet carries half a traceability lot code.
For foods on the FDA traceability list, a lot code is a GTIN and a batch number together — the GTIN says what the food is, the batch says which production run. This pallet has one and not the other, so it cannot be traced. We left the field empty rather than filling it in with half, because a pallet that looks traceable and is not is worse than one that plainly is not.
What to do: Both halves have to come from you: the GTIN from your GS1 company prefix, the batch from whatever assigns lot numbers in your plant. If one is missing from the file, it is missing at the source — check which of the two your system is not sending.
This API key was not given access to that.
A key carries a list of what it may do, and this request needs something the key does not hold. That is usually deliberate: a key minted for an agent, a script or a reporting tool is given the least it needs on purpose, so a mistake or a compromise reaches less. Nothing was changed and nothing was read.
What to do: The response names the missing scope and what it would have allowed. If the key is your own integration’s, mint a new one with that scope. If it belongs to something you gave limited access to, think about whether it should have it before widening it — and call GET /v1/keys/scopes to see what the key does hold.
The request body was missing or not what the endpoint expects.
Either the body was not JSON, or a field the endpoint needs was absent. Nothing was created.
What to do: Send JSON with a `content-type: application/json` header and the fields the endpoint documents. The message says which one was missing.
The number of cartons asked for is not a whole number.
Carton numbers are allocated one per carton, so the count has to be a whole number of at least one.
What to do: Send a positive integer in `count`, or leave it out to get a single number.
That email and password do not match.
Deliberately the same answer for a wrong password, an unknown address, a disabled account and one locked after too many attempts. Telling them apart would let somebody discover who has an account.
What to do: Check the address and try again. After eight wrong attempts an account locks for fifteen minutes, so if you are sure the password is right, wait and retry.
That email address does not look like one.
The sandbox link is emailed, so an address that cannot receive mail means the sandbox would be created and then unreachable.
What to do: Check for a typo and try again.
A location number from GS1 is exactly thirteen digits long.
A Global Location Number is exactly thirteen digits and identifies one physical place. What was entered is a different length, so it was not saved.
What to do: Check the number GS1 issued for the site where your lot numbers are assigned — the plant or packing house, not your head office and not the warehouse you ship from.
That does not look like a GS1 company prefix.
A GS1 company prefix is seven to ten digits and nothing else. The length is not cosmetic — it decides how many cartons you can ever label — so we check it rather than storing whatever arrives.
What to do: Copy it from the certificate GS1 sent. If yours appears with a dash or a space, that is formatting somebody added for reading and is not part of the number.
A barcode number has to be 8, 12, 13 or 14 digits long.
A GTIN is 8, 12, 13 or 14 digits. What was entered is not one of those, so it was not saved. Checked because a GTIN with a digit missing looks complete everywhere downstream and matches nothing during a recall.
What to do: Enter the digits with no spaces, dashes or letters. It is the number under the barcode on your own packaging.
That invite link does not work.
Invites are single-use and expire after seven days, so this one has probably been used or has run out.
What to do: Ask whoever invited you for a fresh link.
One week of this schedule could not be read.
One dated requirement could not be read, so it was left out. The rest of the schedule is intact and usable — one unreadable week must not cost you the other eleven.
What to do: Check that date against what the buyer sent. If the quantity matters, ask them to retransmit rather than guessing at it.
That password reset link does not work any more.
Reset links are single-use and last an hour, so this one has been used already, has run out, or was never a real link. We deliberately do not say which: telling the difference apart would help somebody feeding us guesses work out which of their guesses was once real.
What to do: Ask for another from the sign-in page and use the newest message — asking again replaces any earlier link, so an older one in your inbox will not work. If the address itself is the problem, because somebody has left or a mailbox has changed, we can issue one after confirming who you are by phone.
A key cannot be given more access than the key creating it.
Keys are minted from other keys, and a key may only grant what it already holds. Anything else would mean a limited credential could quietly promote itself, which would make limiting one pointless.
What to do: Mint the key from one that holds the scopes you want to pass on, or ask us. The message names which scopes were refused.
A carton number on this ship notice will not scan.
The SSCC is the eighteen-digit serial number printed on a carton as a barcode, and its last digit is a checksum of the other seventeen. This one does not add up, which means a scanner at the receiving dock will reject it. The rest of the notice was read normally.
What to do: Fix the number in whatever produced the notice before the pallet ships. The message says which digit it should have been. A carton that arrives with an unscannable label has to be identified by hand, and most retailers bill for that.
The file does not say whether it is a test or real.
Every EDI file marks itself as production or test. This one carries neither, so we cannot safely tell whether it represents a real order.
What to do: Ask your partner to set the test indicator correctly. Until then we treat it as test data and will not act on it, which is the safer of the two mistakes.
Technically: ISA15 is neither "P" nor "T".
That invoice number is already on a different order.
Each invoice number can belong to one order. The retailer pays by invoice number, so two orders under one number means one of them is never paid, and QuickBooks would join the two into a single invoice when the file is imported. The message names the order that already has it.
What to do: Use a different number, or leave the box empty and we will number it. Sending the same invoice again for the same order is fine.
The file was cut off almost immediately.
It starts like an EDI file but ends before the header finishes, so we could not even work out which characters separate the fields.
What to do: Ask your partner to resend. A file this short usually means the transfer was interrupted within the first moment.
Technically: The ISA segment is shorter than the 106 characters needed to read its delimiters.
Nothing arrived inside the file.
There was nothing in it to read. Nearly always a transfer that went wrong rather than anything the partner meant to send.
What to do: Ask the partner to resend. If empty files keep arriving, their export is failing.
The file is not quite valid JSON, so it could not be read.
Something in it breaks the format — a trailing comma, a missing bracket, a quote that is not closed. Nothing was lost; the file is stored exactly as it arrived.
What to do: The message says where in the file it stopped making sense. Send that to the partner — whatever generates their file has a bug, and the position is what they will need to find it.
You already have as many of these as we allow.
The caps exist to stop a loop or a script creating thousands of something by accident, not to restrict genuine use.
What to do: Remove one you no longer need, or ask us to raise the limit — we will, if the use is real.
Too many wrong codes, so sign-in is paused for this account.
Someone has entered the wrong second-factor code repeatedly. The pause is what stops a code being guessed, and it applies whether the attempts came from you or from somebody else.
What to do: Wait for the lockout to pass and try again with a fresh code from your authenticator. If you did not make those attempts, change your password once you are back in — somebody knew it well enough to reach the second step. If you have lost the authenticator, use a recovery code.
A product you marked as traceable shipped without a lot number.
You have ticked this product as covered by the FDA Food Traceability Rule, which means every ship notice for it has to say which production lot it came from. The notice was not sent, because one sent without the lot would be accepted by the retailer and useless the day anybody needed it — an untraceable shipment is only discovered during a recall.
What to do: Put the lot number in the Lot box beside that line. It comes from your own production records; we cannot derive it from anything on the order. If the product is not actually on the FDA list, untick Traced under Account, Your products rather than inventing a lot here.
The signature itself was not in the expected form.
The header parsed but the signature inside it is not the right length or encoding, so there is nothing to compare against.
What to do: Check that the value is being passed through unchanged — URL-decoding or lower-casing it will do this. Our documentation has a worked example you can check your implementation against.
An activity figure arrived with no number on it.
A line said what it was reporting — stock available, out of stock — but gave no quantity, so it says nothing either way. That is different from reporting zero, which is a real measurement and is kept. Everything else on the report was read.
What to do: Usually nothing: one blank figure among hundreds is noise. If a particular item or store does it consistently, it is worth telling the retailer, because their own replenishment is reading the same gap.
The memo does not say how much it is for.
BCD04 is empty, so the header gives no amount. Any lines on the memo were still read, and they may add up to the figure that should have been there.
What to do: Compare the lines against the deduction on your remittance. If they match, you have the figure; if the memo arrives this way regularly, it is worth telling the sender, because their own system cannot be reading it either.
The memo has no reference number of its own.
BCD02 is empty. Everything else was read, but there is no number to quote when querying it, which makes a dispute harder than it needs to be.
What to do: Quote the invoice and the date instead. Most senders can find it from those, and it is worth asking them to populate BCD02 for next time.
An adjustment line does not say why the money was taken.
CDD01 carries the reason code — a pricing error, a contested quantity, a damaged return — and this line has none. The amount was still read.
What to do: Query it. A deduction with no stated reason is one you have no grounds to accept, and asking is usually enough: the sender can see the reason even when they did not transmit it.
The order does not identify itself at all.
Every purchase order begins with a segment holding the PO number and the order date, and this one does not have it. There is nothing to identify the order by, so it was not processed. The file is stored exactly as it arrived.
What to do: Ask the partner to resend. A file missing its opening segment is nearly always a transfer that went wrong rather than something their system produced.
Technically: No BEG segment in an 850, or no G50 in an 875.
The invoice does not identify itself at all.
Every invoice begins with a segment holding the invoice number and date, and this one does not. Nothing can be matched to it. The file is stored as it arrived.
What to do: Ask the partner to resend.
Technically: No BIG segment.
The payment advice does not say how much was paid.
An advice of this kind exists to state a payment amount, and this one has none. Everything else in it was read; there is simply no figure to reconcile against.
What to do: Tell us, and we will look at the stored file. An advice with no amount is a bug on the retailer side and they will want to know.
The ship notice does not identify itself at all.
There is no shipment number or date, so nothing can be matched to it.
What to do: Ask the partner to resend.
Technically: No BSN segment.
The ship notice does not say who is carrying the goods.
The notice came through, because the carrier is often arranged separately. Some retailers refuse a notice without one, and a receiving dock that does not know who is coming cannot book a slot.
What to do: Check whether this retailer requires a carrier. If they do, add it; several reject the notice outright without it.
A document that only means something with a date on it arrived without one.
A price change with no effective date cannot be acted on — nobody can tell you when to start invoicing at the new figure. Everything else on it was read.
What to do: Ask your partner when it takes effect before you change anything. Invoicing at a new price a day early comes back as a deduction weeks later.
There is nothing to reference this bill by.
Without a number there is nothing to pay against and nothing to reconcile. The invoice was not processed.
What to do: Ask for a corrected invoice.
Technically: BIG02 was empty.
The invoice does not say which order it is for.
An invoice with no purchase order number cannot be matched to anything, and a retailer whose system cannot match it will not pay it. The invoice came through so it can be corrected, rather than being discarded.
What to do: Add the purchase order number and resend. This is the single most common reason an invoice is rejected or left unpaid.
Technically: BIG04 was empty.
This does not look like an EDI file.
Every X12 document begins with a header we could not find, so we could not read it as EDI. The file is stored exactly as it arrived and nothing was lost.
What to do: Check what your partner actually sent. The usual causes are a PDF or spreadsheet uploaded by mistake, or a file that was compressed or encrypted before it reached us.
Technically: The payload does not begin with an ISA segment.
A line says what to send, but not what it costs.
The order still came through, because an order with no price is still something you can pick and ship. It becomes a problem at invoicing, when there is no agreed figure to bill against.
What to do: Usually nothing immediately. Worth checking the price against your agreement before you invoice, because a retailer who omitted it once will dispute whatever you put there.
A line says what to send but not how much.
That line was refused rather than filled in with a guess. Inventing a 1 would mean shipping one of something a retailer may have wanted five hundred of, and nobody would find out until the delivery arrived.
What to do: Ask the partner for a corrected order. The error names the line, so they can go straight to it.
The order has no line items, so there is nothing to supply.
A header arrived with no products under it. Occasionally this is a cancellation sent in an unusual way; more often the file was cut short in transfer.
What to do: Ask the partner to resend. If they confirm the order really is empty, ask what they intended by it — a cancellation has its own document type.
The ship notice does not say which order it is fulfilling.
Without a purchase order number the retailer cannot match the delivery to anything they ordered, which is the usual cause of a delivery being turned away at the dock.
What to do: Add the purchase order number and resend before the goods arrive.
The retailer sent a response that does not say what it is about.
A response of this kind exists to say "your invoice 30561 was rejected". This one names no document at all, so there is nothing to act on. The file is stored.
What to do: Tell us, and we will look at the stored file. A response naming no document is a bug on the retailer side, and they will want to know.
The order arrived without a purchase order number.
The segment is there but the number itself is empty. Without it there is no way to match the order to anything — not to a shipment, not to an invoice, not to a conversation with the retailer.
What to do: Ask the partner for a corrected file. This is a bug on their side: no retailer system intends to send an unnumbered order.
Technically: BEG03 (850) or G5003 (875) was empty.
A file arrived without saying what to do with its contents.
A price catalogue can be an addition, a change or a deletion, and the field that says which was empty. We have treated it as a change, which is the safe reading: applying a deletion by mistake would remove items the retailer still buys.
What to do: Check with the retailer before removing anything from your own records on the strength of this file.
A line on this schedule asks for nothing.
The part is named but carries no dated requirements. This is usually real — a part being wound down stays on the schedule at zero — so the line is kept rather than dropped, because its absence would be indistinguishable from the part never having been there.
What to do: Nothing, usually. If you expected a requirement for this part, check the schedule against what the buyer sent.
Routing instructions arrived without the number that ties them to your request.
When you ask a retailer where to send a load, your request carries a control number and their answer is supposed to quote it back. This answer did not, so it cannot be matched automatically to the request it belongs to. The instructions themselves — carrier, dates — were read normally.
What to do: If you have more than one routing request outstanding, check the purchase orders on the instruction to work out which load it is for before releasing the freight.
There is nothing to build from this one.
A planning or shipping schedule with no LIN lines asks for nothing. That is occasionally deliberate — a buyer clearing a horizon — but far more often it means the transmission was cut short.
What to do: Check with the sender before acting on it. Treating an empty schedule as "build nothing" when it was actually truncated stops a line.
The order does not say where it is going.
There is no ship-to party, so whoever picks this order has no destination. The order came through, because the rest of it is usable and the address is often on a separate document or standing instruction.
What to do: Check whether this partner normally sends a destination. If they do, ask for a corrected file; if they never do, the delivery address is part of your arrangement with them rather than part of each order.
Technically: No N1 segment with a ship-to qualifier.
The ship notice has no shipment number.
The retailer receiving the goods uses this to match the delivery to the paperwork. Without it, the pallet arrives and nobody knows what it belongs to.
What to do: Add the shipment number and resend.
Technically: BSN02 was empty.
A line on the ship notice does not say how many were shipped.
The receiving dock counts against this figure. A line without one will be queried, and queried deliveries get held.
What to do: Add the shipped quantity for that line and resend.
A carton on this ship notice has no number at all.
Every carton on a notice should carry its own SSCC, because that is what the retailer scans on arrival and matches against what you told them was coming. This one has none, so there is nothing for them to match and no label we can print for it.
What to do: Add an SSCC for the carton in whatever produced the notice. If your system does not generate them, we can — they are built from your GS1 company prefix and a serial number you count up, and we only need the prefix once.
The invoice does not state a total.
The lines are there but the total is not. Most retailer systems reject an invoice with no total outright.
What to do: Add the total and resend. It should equal the line amounts; if it does not, settle which figure is right before sending.
Technically: No TDS segment.
We have no GS1 company prefix for this account.
Carton numbers are built from your own GS1 company prefix — the same one behind your product barcodes — and we have none on file, so there is nothing to build them from. Nothing else about your account is affected.
What to do: Send us the prefix from your GS1 certificate, or set it yourself with PUT /v1/sscc/prefix. If you have never been issued one, GS1 issue them directly; it is the one number in EDI that cannot be borrowed, because numbers built from someone else’s prefix identify their company rather than yours.
The label preview was asked for a carton beyond the end of this notice.
The label preview was asked for a carton this ship notice does not have. Cartons are numbered from one, and only cartons that can actually be labelled are counted — if some were rejected for a bad SSCC, the printable ones are still numbered one upwards with no gaps.
What to do: Ask for a number between one and the carton count shown on the notice. If you expected more cartons than it has, the ones missing are listed with their reasons, and each is something to fix in whatever produced the notice.
This connection signs in with a password rather than a key.
FTP and FTPS authenticate with a password the retailer issues. SFTP uses a keypair we generate and hold, which is why a new key can be made here for one and not the other.
What to do: Ask the retailer for a new password, then open a ticket and we will set it. We cannot generate a credential that is theirs to issue.
That setting belongs to a person, and this request came from an API key.
Notification settings decide who we email, and an API key has no inbox. The key itself is working — it simply is not the kind of caller this setting is about.
What to do: Sign in to the portal and change it there. Everyone on the account sets their own, so changing it as one person does not alter what anybody else is told.
That document is not an order, so there is nothing to answer.
A ship notice and an invoice both answer a purchase order: the part numbers, prices and ship-to all come from it. The document you picked is something else — an acknowledgment, a remittance, or a notice we sent you.
What to do: Open the purchase order you are shipping against and confirm that instead.
Carton labels only come from a ship notice.
Labels describe what is in a carton and where it is going, and only a ship notice (856) says that. An order or an invoice describes the commercial transaction, not the pallet.
What to do: Open the ship notice for this shipment and print the labels from there. If you have not sent one yet, the labels and the notice are produced together, so creating the notice is the first step either way.
This account has no second factor set up.
A code was offered for an account that is not enrolled, so there is nothing to check it against.
What to do: Sign in with your password; you will be taken through setting up an authenticator. Staff accounts must have one, because a staff account can read every customer’s documents.
This file has not been read into a document yet.
The bytes are stored exactly as they arrived and nothing has been lost, but the document has not been parsed, so there is nothing yet to make labels from.
What to do: If it arrived in the last few moments, try again shortly. If it never parsed, the errors listed on the document say why, and each one explains what to do.
This account cannot do that.
The action is not available for this account type.
What to do: Email hello@palletlabs.org and we will explain why and what the options are.
There is no paper form of this document.
Orders, invoices and ship notices print. An acknowledgment is a receipt for a machine — printing one would hand somebody a page that cannot tell them anything they can act on, so it is refused rather than rendered as a mostly empty sheet.
What to do: Read it on screen instead. If you need a paper record that a document was acknowledged, print the document it acknowledges — its status is shown there.
Your session has expired after twelve hours.
Sessions last twelve hours, and this one has expired or been signed out.
What to do: Sign in again. Nothing you had open was lost — the portal reads your data fresh each time, so nothing was part-way through being saved.
Every line is zero, so there is nothing to tell the retailer.
A ship notice says what left the building. With no quantities on it, there is nothing for the retailer to receive against.
What to do: Put quantities against the lines that shipped. If the order was cancelled rather than shipped, that is an order acknowledgment and a different conversation — tell us and we will send one.
Every line is zero, so the invoice would be for nothing.
An invoice bills for what shipped, and nothing is marked as shipped.
What to do: Put quantities against the lines you are billing for.
The preview was asked for without saying what to preview.
A rehearsal has to be a rehearsal of something. The request named a document to answer but did not ask for a ship notice or an invoice, so there was nothing to build.
What to do: Ask for one or both: send `ship: true`, `invoice: true`, or both together. Nothing was sent or stored either way — a preview never is.
No carton on this notice can be labelled.
Either the notice lists no cartons at all, or every carton on it has a problem with its SSCC. We will not print a blank or a guessed barcode, because a carton that arrives and scans as nothing costs more to sort out than one that never shipped.
What to do: The reason for each carton is listed with the error. Every one of them is something to fix in whatever produced the notice — most often a missing SSCC, or one whose check digit is wrong.
Part of a document arrived with nothing for it to belong to.
A detail — a quantity, a date — appeared before the item it describes. We kept the rest of the document and left that detail out rather than attaching it to the wrong item, which would be worse than losing it.
What to do: Usually a fault at the sending end. If a figure looks missing, the stored original shows what actually arrived. Open a ticket and we will read it with you.
The file is bigger than this partner accepts in one go.
Some retailers cap how much one document may carry — Kroger allows 250 items on a price change, 250 on a promotion, and 150 stores on a direct-store-delivery promotion. This one is over. We have read all of it, so nothing is lost on our side.
What to do: If the retailer rejected it, this is why, and it needs splitting into several documents. If they accepted it, no action is needed.
Too many requests from here in a short time.
Each demo sets up a real account on our servers, so there is a limit on how many one person can start. Nothing is wrong with your request.
What to do: Wait a few minutes and try again. If you need several sandboxes for a team, tell us and we will set them up directly instead.
The payment does not match what the lines on it add up to.
The retailer sent a payment and a list of what it covers, and the two do not agree. This is not an error on our side and not necessarily one on theirs — but it does mean part of what you were paid, or not paid, is not explained by anything in the advice.
What to do: The message gives both figures. Take the difference to your retailer contact: an unexplained gap is almost always a deduction they have applied without itemising it, and it is much easier to query now than at the year end.
Technically: The RMR amounts do not sum to BPR02.
That change is made by somebody signed in, not by an API key.
How people sign in to your account is changed from the portal by a person. An API key has no password to re-confirm with, and a key that could switch off everybody’s second factor would be a strictly better target than the passwords it protects.
What to do: Sign in to the portal and change it there. If you are automating account setup, this is the one thing deliberately left out of the API.
Demo sandboxes cannot do this.
Sandboxes are created automatically by the demo form with no review, so they cannot create SFTP logins, request AS2 connections, or add delivery destinations. Everything else works.
What to do: Upload files and read the results to see the whole pipeline. Email hello@palletlabs.org when you want a real account.
A document inside the file was never finished.
One of the documents has a beginning but no end. We did not process it, because a partial purchase order is worse than none.
What to do: Ask your partner to resend. If only one document in a batch is affected, their system may have failed part-way through writing the file.
Technically: An ST opened a transaction set with no matching SE.
A document ends without ever having started.
There is a closing marker for a document with no opening. The file structure is inconsistent, so we did not process that part.
What to do: Ask your partner to resend the file.
Technically: An SE segment appeared with no open transaction set.
A document states a different length than it turned out to be.
Each document records how many lines it should contain, and this one does not add up. Lines may be missing, so we did not process it — a purchase order with lines missing is the most expensive kind of mistake here.
What to do: Ask your partner to resend. Tell them which document reference was affected; their software logs it under the same number.
Technically: SE01 does not equal the number of segments in the transaction set.
A document opens and closes with different reference numbers.
The start and end of one document disagree, so we cannot be sure the content belongs to the document it claims to be.
What to do: Ask your partner to resend the file.
Technically: SE02 does not match ST02.
Type a bit more before we look.
A query made only of wildcards would match every document you have, which is a slow way of asking for the list you already get by clearing the search box.
What to do: Type at least two real characters. `*` stands for any run of characters and `?` for exactly one, so `PO-884*` and `PO-8841?` both work.
There is content outside the document structure.
Something appears in the file where nothing should — often a stray line added by a transfer tool. Everything is stored exactly as received.
What to do: Usually harmless and safe to ignore. If documents are also failing, ask your partner whether anything is post-processing the file after their EDI system writes it.
Technically: A segment appeared where the envelope structure does not permit one.
The webhook signature did not match.
The body and the signature disagree. The usual cause is signing a re-serialised copy of the JSON rather than the exact bytes received — adding or removing a space changes the signature completely. The other cause is the wrong signing secret.
What to do: Sign the raw request body, before any JSON parsing, and check you are using the secret for this endpoint rather than another one. Treat the request as untrusted until it verifies.
A document sits outside its section.
A document appears where the file structure does not allow one. We kept everything and recorded where the problem is.
What to do: Ask your partner to resend. Their software is producing a malformed structure.
Technically: An ST segment appeared outside any GS functional group.
The stated total does not match what the lines add up to.
Both figures are in the document and they disagree. We report it rather than picking one, because choosing silently would mean either the retailer or you being billed the wrong amount with nothing recording the decision.
What to do: Work out which figure is right before this is paid. The usual causes are an allowance or charge left out of the total, or a line amended after the total was calculated.
A column the layout expects is not in the file.
The partner has most likely renamed or removed a column. We did not guess which other column was meant, because reading a price out of the wrong one is worse than reading nothing. The file is stored and can be run again once the layout is corrected.
What to do: Tell us, or compare the file against what the partner sent last time. Correcting a layout takes minutes and the stored file is reprocessed afterwards, so nothing is lost.
The column that separates one order from the next is not in the file.
Without it there is no way to tell where one order ends and the next begins, so the file was not read. Nothing was lost.
What to do: Tell us. This nearly always means the partner renamed that column, and correcting the layout takes minutes.
A row does not say which order it belongs to.
That row was left out rather than attached to whichever order came before it, which would have added somebody else’s line to an order.
What to do: Look at the line named in the stored file. A blank row at the end of a spreadsheet is the usual cause and is harmless.
The file has nothing in it where the layout expects an order.
Either the partner changed the shape of their file or the layout is out of date. The file is stored and can be run again once that is settled.
What to do: Tell us, and if you can, attach what the partner sent previously for comparison.
The file has a heading but nothing under it.
There were no orders in it. This is usually a scheduled export that ran on a day with nothing to send.
What to do: Normally nothing. If orders were expected, ask the partner whether their export ran correctly.
An order in the file has no line items where the layout expects them.
That order was reported rather than passed on with no lines, because an order with nothing on it cannot be fulfilled and would look like a real one. The file is stored and can be run again.
What to do: Tell us. The partner having renamed the part of their format that holds line items is much the most likely cause.
None of the lines in an order could be read.
Every line was missing something it cannot do without, so there was no order left to pass on. The errors above this one say what was missing on each.
What to do: Ask the partner for a corrected file. If every line is missing the same thing, it is a change on their side rather than a bad file.
Something the layout expects is not in the file.
The partner has most likely renamed part of their format. We did not guess at a substitute. The file is stored and can be run again once the layout is corrected.
What to do: Tell us. The message names exactly what was looked for, which is usually enough for us to correct the layout the same day.
Technically: No element or attribute matched the declared path.
Something the order cannot do without was sent empty.
That line was left out rather than filled in with a guess. A line with no quantity cannot be fulfilled, and inventing a 1 would be the worse of the two failures.
What to do: Ask the partner for a corrected file. If the field is genuinely optional for this partner, tell us and we will relax the layout.
A value in the file is not the kind of thing it should be.
A quantity that is not a number, or a date that does not fit the layout the partner uses. That value was refused rather than guessed at.
What to do: Look at the line named in the stored file. If the partner has changed how they write dates, tell us — that is a layout change rather than a problem with the file.
The webhook is too old, or your clock disagrees with ours.
Signatures carry a timestamp so an old request cannot be captured and replayed later. This one is outside the window — either it was genuinely delayed, or the clock on the receiving machine has drifted.
What to do: Check the clock on the receiving server first; drift is the common cause and it affects more than webhooks. If the clock is right, the request really was delayed and we will redeliver it.
The file is larger than we accept in one go.
A file answering orders can be up to 2 MB. Nothing in this one was sent.
What to do: Split the export into smaller files, for example one per day or per retailer, and send each.
That is more carton numbers than we will issue in one request.
Every number issued is gone for good — we never reissue one — so a single request that asks for an enormous batch is either a mistake or a loop with a wrong variable in it, and both would quietly consume a range that cannot be recovered.
What to do: Ask for what the shipment actually needs, in batches of up to a thousand. There is no penalty for calling repeatedly.
That feature is switched off on this deployment.
The endpoint exists but is disabled here — most often the self-service demo on an installation that does not run one. Your request was not the problem.
What to do: Contact us and we will do directly whatever the endpoint would have done.
The retailer used a response code we do not recognise.
We could not tell whether they accepted or rejected the document, so it is reported as needing attention rather than assumed to be fine. That is deliberate: telling you an invoice was accepted when we could not actually tell is the one mistake here that would cost you money quietly.
What to do: Look at the document in your history and check with the retailer. Send us the code and we will add it, so this answers itself next time.
Your retailer changed a line in a way we do not have words for yet.
An order change says what to do with each line using a two-letter code — reduce it, cancel it, add one. This document used a code that is not in our list, so the line is shown marked "unrecognised" with its new quantity and price, rather than guessed at or dropped. Everything else on the change was read normally.
What to do: Look at that line in the document and check with your retailer what they intended before you ship against it. Send us the code and we will add it, so it reads in plain English next time.
We could not tell whether an amount was being added or taken off.
An allowance or charge arrived with a marker that says neither "allowance" nor "charge". The amount is kept and recorded as a charge, so nothing is lost — but the direction is a guess, and on an invoice the direction is the difference between being paid more and being paid less.
What to do: Check that line against what the partner intended before this is paid or claimed. Send us the marker they used and we will recognise it next time.
Technically: SAC01 was neither A nor C.
A field that should hold one of a short list of codes held something else.
Some fields carry a code from a fixed list — whether an adjustment came from the store or from you, what kind of price a figure is. This one carried a value that is not on the list. We kept the surrounding information and said so here rather than picking whichever meaning seemed likely, because the two meanings are usually opposites.
What to do: Read the document before acting on it, and check with your partner what they meant. Send us the code and we will add it.
A requirement uses a commitment code we do not recognise.
The code is reported exactly as sent rather than guessed at. Commitment is the field you plan against — firm means build it, planned means expect it — and assuming the wrong one would have you building something nobody ordered or missing something they did.
What to do: Check the code against your buyer’s implementation guide and tell us what it means. We will map it so it reads properly from then on.
One of those lines is not on this purchase order.
A ship notice and an invoice can only answer lines the retailer actually ordered. A line number that is not on their order will be rejected by them even if we send it — and an invoice for an unordered line is a deduction waiting to happen.
What to do: Check the line numbers against the order. If you shipped something they did not order, that needs agreeing with them before it is invoiced, not after.
A stock figure arrived labelled with a code we do not have words for.
An inventory report states each number with a code saying which number it is — available to sell, on hand, damaged, in transit. One of these used a code that is not in our list. The figure is kept and shown with the raw code rather than dropped or guessed at, because guessing could show damaged stock as sellable.
What to do: Check with your partner what that code means before relying on the figure. Send it to us and we will add it, so it reads in plain English next time.
The file uses an EDI version we do not support yet.
We read the file but do not have the rules for this version, so we have not translated it. The original is stored and nothing is lost — we can process it once support is added.
What to do: Tell us which version your partner is sending. We currently support 004010, with 005010 next. This is on us, not on you.
Technically: ISA12 names an interchange control version this build does not recognise.
We cannot re-read our stored copy of this ship notice.
The original file is intact and nothing has been lost. The stored interpretation of it will not load into the shape the label printer needs, which is a problem on our side rather than with anything you sent.
What to do: Raise a ticket and we will look at it. If the pallet is waiting, say so and we will treat it as urgent.
That kind of document is not one we read yet.
The file arrived intact and is stored. It simply has no mapping on our side, so no canonical document was produced — nothing was lost and nothing was rejected.
What to do: Tell us which document type you need. Adding one is a known, bounded piece of work, and the file you already sent will be reprocessed once it exists.
That SFTP username is already in use.
SFTP usernames are global across all customers, because they are logins to one shared server.
What to do: Choose a different name. Your account prefix is added automatically.
A numeric character code in the file is not a real character.
It was left as written rather than guessed at. One value may read oddly; the rest of the file was read normally.
What to do: Usually a corrupted transfer. Ask the partner to resend; if it happens twice, the problem is in whatever generates the file.
Technically: A numeric character reference was out of range or unparseable.
The file asks us to load something from elsewhere, so it was refused.
We did not read it. A file can use this to make a server fetch private files or run out of memory, and there is no version of a purchase order that needs it — so we refuse rather than try to handle it safely. The file is stored exactly as it arrived.
What to do: Ask the partner to send the file without the DOCTYPE line at the top, or with any special characters written out directly. Most systems have an option for this; it is usually a one-line change on their side.
Technically: The document declared a DOCTYPE with an internal subset or a SYSTEM/PUBLIC identifier. Entity expansion is not supported at all: this is the XXE and billion-laughs surface.
Nothing arrived inside the file.
There was nothing in it to read. This is nearly always a transfer that went wrong rather than anything the partner meant to send.
What to do: Ask the partner to resend. If an empty file keeps arriving, their export is failing.
The file looks like several files joined together.
A file of this kind holds one outermost document, and this one has more than one. We read the first and reported the rest rather than merging them, because merging two partners’ orders would be worse than reading neither.
What to do: Ask the partner to send each document as its own file, or tell us the element that wraps them and we will read them as a batch.
Technically: A second root-level element was found.
The file has no content in it at all.
There was text in the file but nothing readable as a document. Nothing was lost; the file is stored as it arrived.
What to do: Check whether this is the right file. A header-only export or a stray log file is the usual cause.
Technically: No elements were found in the document.
There is loose text outside the document in the file.
Something has been added before or after the document itself — often an error message from the partner’s own system that ended up in the file. Nothing was lost.
What to do: Open the stored file and look at the text. It frequently explains the real problem on the partner’s side better than anything we could say.
Technically: Non-whitespace character data appeared outside the root element.
A block of literal text starts and never ends.
The file is cut short, so the rest of it could not be read.
What to do: Ask the partner to resend.
Technically: A CDATA section was opened and never terminated.
The line at the top of the file never finishes.
The file is cut short at the very beginning, so none of it could be read.
What to do: Ask the partner to resend.
Technically: An XML declaration or processing instruction was not terminated.
A declaration near the top of the file never finishes.
The file is cut short near the beginning, so none of it could be read.
What to do: Ask the partner to resend.
Part of the file opens and is never closed.
The file is almost certainly cut short, so some of what the partner sent is simply not there. Nothing we did read was lost.
What to do: Ask the partner to resend. A truncated file is a transfer problem rather than a formatting one, and resending usually fixes it.
Technically: An element start tag had no matching end tag by the end of the document.
A tag in the file starts and never finishes.
The file is cut short. Everything up to that point was read.
What to do: Ask the partner to resend.
Technically: A tag was opened and the document ended before its closing bracket.
The file closes something that was never opened.
One part of the file is out of order. We read what we could and reported this rather than guessing what was meant.
What to do: Ask the partner to resend. If it happens repeatedly, whatever generates their file has a bug and they will want to know.
Technically: A closing tag matched no open element on the stack.
The file uses a shorthand for a character that we do not recognise.
That shorthand was left exactly as written rather than guessed at, so a value may contain something like the literal text of the code instead of the character meant. Everything else was read normally.
What to do: Ask the partner to send the character itself rather than a shorthand for it. Curly quotes and dashes in product descriptions are the usual cause.
Technically: A named entity other than amp, lt, gt, quot or apos was referenced. Custom entities are not expanded, by design.
Part of the file is damaged and does not say what it is.
That part could not be read, which almost always means the file was corrupted somewhere in transfer. Everything else in it was read normally.
What to do: Ask the partner to resend. If the same damage appears twice in a row, the problem is in whatever writes the file rather than in sending it.
Technically: A start tag contained no element name.