← OrderSync EDICONTENT HISTORY
WHAT CHANGED
Update to OrderSync EDI
Snapshot Nov 5, 2026 · 01:19 UTC · version 1.0.3
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save OrderSync EDI and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Check and correct UPC, EAN, GTIN, GLN or SSCC numbers, singly or in bulk from a list or spreadsheet column. Use when the user asks whether barcode numbers are valid, needs check digits calculated or fixed, has a spreadsheet column of UPCs to clean up, or wants case (GTIN-14) codes for their UPCs before sending a catalog, PO, ASN or carton labels.",
"included_files": [],
"name": "gs1-barcode-check",
"skill_md_contents": "---\nname: gs1-barcode-check\ndescription: Check and correct UPC, EAN, GTIN, GLN or SSCC numbers, singly or in bulk from a list or spreadsheet column. Use when the user asks whether barcode numbers are valid, needs check digits calculated or fixed, has a spreadsheet column of UPCs to clean up, or wants case (GTIN-14) codes for their UPCs before sending a catalog, PO, ASN or carton labels.\n---\n\nUse this workflow for GS1 identifiers. The user's own instructions take priority over these steps.\n\n## Steps\n\n1. Collect the numbers exactly as the user gave them, blank rows included. For a pasted table or file, take the column of identifiers and keep row order, so row numbers in the result match their spreadsheet.\n2. Call `check_gs1_identifiers` with up to 500 numbers per call. For more, call it again with the next batch.\n - Numbers without their check digit (7, 11, 12, 13 or 17 digits): use `mode: \"add_check_digit\"`.\n - Case or inner-pack codes: ask for the indicator digit (1 to 8, one per packaging level) and pass it as `pack_indicator`. A unit UPC padded to 14 digits is still the unit's code, not a case code.\n3. Report by cause, with row numbers, in the order the tool gives:\n - Wrong check digits, with the recalculated value marked \"verify\".\n - Missing digits: values a spreadsheet damaged by dropping leading zeros, or bodies sent without a check digit. When two readings fit, give both and ask which is right; never pick one.\n - Scientific notation (e.g. 6.14141E+11): the digits are lost; ask for the column re-exported formatted as Text.\n - Values that are not GS1 numbers (letters, wrong length): usually part numbers in the wrong column.\n - Blank rows and duplicate numbers.\n4. When the user wants the corrected list back, keep their order and give original, suggested and status columns, so they can see what changed. The widget's \"Copy for spreadsheet\" does this.\n5. Next steps: new SSCCs come from `generate_sscc_numbers`; carton labels from `create_sscc_labels_pdf`.\n\n## Rules\n\n- The tool checks arithmetic only. A correct check digit does not mean the number is registered to the user's company; say so if the user asks about ownership.\n- Never \"fix\" a number by changing digits other than the check digit. A recalculated check digit is a suggestion: a mistyped digit elsewhere gives the same error, so the user confirms it against their item master or GS1 account.\n- If values look like spreadsheet damage (11 digits, or E+ notation), say so and ask for the column re-exported as Text.\n"
}SHA-256 of public snapshot: 8aa7a043f9cb0f87bad1fb701d797fa72e60b33ab7ae50649b80e40a87340db5