DYMO Label Templates: Dates & Serial Numbers
Share
Quick answer: Use a Date and Time object only when the label needs the print-time value. Preserve historical dates as record values, and reserve and reconcile counter ranges so reprints do not create duplicate identifiers.
A reusable label template should preserve the design while making the changing information obvious. Decide which fields are permanent, which come from a record and which should be generated when you print. Those distinctions matter for dates and serial numbers. Today's print date, an item's inspection date and its next scheduled review date are different values, even if they use the same visual format.
Separate the three kinds of content
| Content type | Example | Control |
|---|---|---|
| Fixed wording | ASSET ID | Template text |
| Record-specific value | Previously assigned asset number | Imported data or entered value |
| Print-time value | Current print date | Date and Time object, where appropriate |
| New sequence | Consecutive temporary tags | Counter with controlled starting point |
Do not use a live date where the label needs to preserve an earlier event date. Reprinting that label later could otherwise show the reprint date instead of the event.
Save an ordinary layout first
Select the correct label format and create the fixed text and objects. Print one sample with representative values. Once spacing is satisfactory, save the design with a name that identifies format, purpose and revision. For example: 30334_asset-tag_v1 30252_internal-routing_v2
Keep the approved version in a shared location employees can identify. Store experiments under different names so the next operator does not accidentally choose an unfinished variant.
Add a current date or time deliberately
In DYMO Connect, use Add > Date and Time, then configure the selected object's properties. The Connect guide documents automatically updated date/time objects.
Choose an unambiguous displayed format for your team. If labels travel between sites, confirm what the time means and check the computer's clock before production. A timestamp printed from the wrong system clock is still neatly formatted incorrect information. For a historical inspection date or scheduled future date, use an explicit record value instead. Label the field clearly, such as “Inspected” or “Review due,” so a reader does not have to guess.
Create and verify a sequence
Use Add > Counter. In its properties, set the start number, increment and any prefix, suffix or leading zeros. Then set the quantity for the series using the control beside Print, as described in the guide. For a fictional temporary-tag run:
- Prefix: CHECK-
- Start: 101
- Increment: 1
- Digits: 4
- Quantity: 3
- Expected output: CHECK-0101, CHECK-0102, CHECK-0103
Print that small trial and verify all three values. Do not assume a saved counter automatically manages a business-wide registry or prevents another computer from issuing the same range.
Prevent duplicates on repeat runs
Before a numbered job, reserve its intended range in your team's record. Afterward, record the last successfully issued identifier and any spoiled labels. For permanent asset IDs, importing an authoritative list may be safer than generating independent sequences on multiple workstations. A jam makes numbering especially important.
Reconcile physical labels with the job record before restarting. Reprinting an entire range can produce duplicates even if the printer itself works correctly.
Hand off the template with a short note
Include its intended printer, roll format, editable fields and date behavior. For counters, state who assigns the next starting number. For imports, state the required column names. Reopen the saved file and print a fresh sample before declaring it the team's standard. That catches missing fonts, altered objects and assumptions that were only true in the original editing session.