Answers to the questions that come up most when converting a GCSS-Army BOM into a DD Form 1750 Packing List.
What does this tool actually do?
It reads a GCSS-Army BOM (Bill of Materials) or hand receipt PDF, pulls out the line items, NSNs, descriptions and quantities, and fills them into an official DD Form 1750 Packing List that you can review, edit, and download as a ready-to-print PDF.
What file formats are accepted?
Two GCSS-Army BOM layouts are supported and detected automatically — no need to pick one: the Component Listing / Hand Receipt export, and the Army Data Platform BOM report. Both must be the native PDF export from the source system, not a printout that's been rescanned.
Why can't I upload a handwritten or scanned BOM?
This tool reads the data layer embedded in a native PDF export — there's no OCR step. A scanned or handwritten document has no such data layer, so there's nothing for it to extract, and results would be unreliable even if something came out.
Which quantity ends up on the 1750 — AUTH Qty or OH Qty?
On Hand (OH) Qty is used when the source document provides it. When it isn't present — which is the case for most BOM exports — Authorized (AUTH) Qty is used instead. Either way, the value always lands in the Total column; Initial Operation and Running Spares are left blank, since the source BOM doesn't split quantities that way.
What happens to my file after I upload it?
Processing happens for your session only. Nothing from the uploaded document is stored after you leave the page, and CUI markings on the source carry through to the generated 1750 unchanged.
What's the difference between an "excluded" item and a "flagged" item?
Excluded items are left out of the generated 1750 entirely — usually a COEI/BII section marker row, not a real line item. Flagged items are still included, but something about that line (a missing NSN, an unusual quantity shape, etc.) couldn't be resolved with full confidence, so it's called out for you to double-check before generating.
What are those COEI / BII dividers in the item list?
GCSS-Army BOMs mark "Components of End Item" (COEI) and "Basic Issue Items" (BII) sections with a marker row rather than a real line item. Those markers aren't packable items, so they're excluded from the 1750 — but every real item that follows one is tagged so the review list shows it as a labeled section instead of losing that grouping.
Can I edit anything before generating the PDF?
Yes. Every extracted field is editable on the Review & Edit step — descriptions, identifiers, quantities, and the header fields (Packed By, boxes, requisition/order numbers, end item, date) — and you can exclude or un-exclude any line before generating.
Why is the description text tiny on some lines?
Long descriptions auto-shrink to fit their box on the printed form rather than getting cut off — the form guarantees the full text stays visible, even if that means a smaller font on an unusually long line. If you find a specific line hard to read, you can shorten the description on the Review & Edit step before generating.
Is this an official Department of Defense or Army tool?
No — this is an independent tool built to save time filling out DD Form 1750s from GCSS-Army exports. Always review the generated form against your source BOM before signing and submitting it.
I found a bug, or my BOM didn't extract correctly — what do I do?
Double-check that the PDF is the native export (not a scan) and try again. If it still doesn't work, hold onto the file so the issue can be reproduced — this tool is actively maintained and edge cases in new BOM layouts get fixed as they're found.