Shopify Line Item Properties for Personalized Products
If you sell engraving, monograms, color choices, or “add a note” on Shopify, you are already using line-item properties — even if you never called them that.
They are the little key/value pairs attached to a line item: Engraving = “Sarah”, Finish = “Gold”, Proof = filename.jpg. Themes, product options apps, and custom checkout fields write them. Your production process has to read them.
This post is a practical tour for makers: what properties are, how to name them so production does not cry, and how to stop mining them one order click at a time.
Properties vs variants vs line item notes
Quick distinctions that save confusion:
- Variants — structured SKUs (size, color) with inventory. Great when stock differs.
- Line-item properties — arbitrary customization for this unit. Perfect for unique engraving text.
- Order notes / attributes — cart-level or order-level comments. Easy for customers to find, awkward when two personalized items share one note.
For true personalization, properties on the line item win. Each piece carries its own instructions.
What good property design looks like
Think about the person reading the field at the bench — maybe you, maybe a helper, maybe a printed sheet.
Use stable keys
Prefer Engraving, Monogram, Finish across products. Avoid renaming the same idea to Text, Message, and Personalization on three SKUs unless you enjoy mapping tables.
Constrain values when you can
Finish should be a dropdown (Gold / Silver / Rose), not free text “kinda goldish.” Engraving is free text by nature — that is fine — but anything that should be batchable should be structured.
Label for humans
The key shows up in admin and in production tools. eng_txt_v2 is clever until you are tired. Engraving is better.
Separate concerns
Do not cram “Gold — Sarah — gift wrap” into one property. Split Finish, Engraving, and Gift wrap so you can sort and validate each.
How properties show up in admin (and why that hurts)
In Shopify admin, properties live on the line item inside the order. To review forty engravings you open forty orders (or use a bulk export). That is the open-read-close loop personalized shops drown in.
Packing slips can print properties if your slip template includes them — useful at pack time, late for production planning.
So makers either export, or they install something that surfaces properties in a work queue.
Production needs a property-first view
A packing view asks: what goes in which box? A production view asks: what text goes on which blank?
Same data. Different arrangement.
For production you want:
- Every open custom line across orders
- Property columns visible
- Group by product or by a property value (all Finish=Gold)
- Mark produced without fulfilling
- Optional paper run sheet
That is exactly the gap Maker’s Production View fills for hand makers. It turns unfulfilled orders into a live queue with customizations on one screen, batching, produced status, run sheets, and engraving flags — without treating the bench like a CRM.
Privacy note while we are here
Properties are product instructions. Customer shipping fields are personal data.
Your engraver needs “Sarah” on the necklace. Your engraver does not need the customer’s phone number on the same screen. Apps and exports that dump everything onto a shared workshop device create risk for no production gain.
Prefer tools that read orders for line items and properties and keep customer PII out of the floor view. That is a deliberate choice in Maker’s Production View: orders only for the queue, no customer names/addresses/emails/phones on the production UI.
Common property setups for maker shops
Engraved jewelry
- Engraving (text)
- Font (optional dropdown)
- Finish
- Chain length (variant or property)
Monogram gifts
- Monogram letters
- Monogram style
- Thread / color
Personalized prints / tags
- Name line
- Date line
- Proof upload (file property)
Small MTO apparel
- Name on cuff
- Number
- Size (usually variant)
Whatever you sell, write the property list down once and reuse it. Consistency is a production feature.
Validating before checkout vs catching after
Theme or app validation can block emoji, limit character counts, and require fields. Do that when you can — it prevents bad orders.
Still assume something will slip through. Post-order scanning of engraving fields (flags for emoji/special characters) is your second seatbelt. Validation reduces volume of problems; queue flags catch the rest before you cut.
Getting properties into hands, not just into data
Data in Shopify is not work on the bench until someone can see it in the right shape.
If your current flow is “open order → squint → sticky note,” properties are working for checkout but failing production. Fix the read path.
Maker’s Production View is built to read those properties into a maker-friendly queue — $15/month, 14-day trial. Background on the product lives at fleartex.com.
Name the fields clearly. Keep them on the line item. Then look at them as a batch, not as forty separate tabs.