Data Matrix for parts and electronics marking
Direct part marking -- laser-etching or dot-peening a symbol straight onto a component -- works at a fixed physical size decided by the marking head, not by the printer settings a label print job would use, so the render size itself is the thing to configure ahead of time rather than leaving it to auto-scale.
Preconfigured for small-part marking
This experience renders at a 1x module scale ("scale": 1) -- the smallest per-module pixel size bwip-js exposes -- so the exported PNG maps as closely as possible to a single mark unit on your DPM equipment; you will still typically scale the export to your marking head's actual physical resolution.
Example data
The generator is seeded with "Data Matrix for small part marking", distinct from the primary's "This is Data Matrix!"; replace it with your own part or serial number.
Workflow
Enter the part/serial identifier, confirm the preview at your intended print size, then export SVG for laser marking or label printing.
Job-specific settings
Choose a fixed version if your marking equipment requires a specific module count, rather than letting size float automatically.
Marking notes
Data Matrix needs only a narrow quiet zone, which is part of why it suits direct part marking on small components.
Common mistakes
Oversized data for a fixed version is the most common failure; increase the version or shorten the payload.
Standard
Data Matrix (ECC 200) is defined by ISO/IEC 16022.
Related
For product traceability with GS1 application identifiers, use the GS1 Data Matrix generator instead.
FAQ
Is a laser-etched or dot-peened mark still ECC 200 Data Matrix?
Yes -- the marking method (ink, laser, dot-peen, or chemical etch) doesn't change the underlying symbology; bwip-js only produces the module pattern, and separately verifying the physically marked result's contrast and quiet zone with your own equipment's reader is still worthwhile since marking quality varies by material.