Are there specific formatting requirements for GS1 field 8012?

Anonymous · Published September 22, 2025 · 2 comments

Does anyone know if there are specific formatting requirements for GS1 field 8012, especially for software versioning? At our company, we considered using code 240, but our software is modular and our versioning looks like DX5.1-CO5.2-KL5.2. Is there a required format for 8012, or is it flexible?

Join the discussion. Leave a comment. Guest comments are welcome — add your email to get reply notifications.

Laura Fischer 9 months ago

Is use of 8012 mandatory, or could other codes like 10 or 240 be used for software?

Reply to this comment

Peter Müller 9 months ago

Is the answer different if we use EU standards versus FDA requirements?

Reply to this comment

Discussion

4 Answers

Accepted answer available

Accepted answer Dr. Oliver Eidel · Founder & CEO, OpenRegulatory · 9 months ago

There is no set format for field 8012. According to the GS1 General Specifications (see pages 210-211), the field can contain any alphanumeric values and a range of other symbols. So you can use your modular versioning scheme as needed.

Join the discussion. Leave a comment. Guest comments are welcome — add your email to get reply notifications.

No comments yet. Be the first to share your thoughts.

Anonymous · Software Engineer, SoftMedix GmbH · 9 months ago

I'm not aware of any specific formatting requirements for 8012. We just use our typical software version format and haven't encountered any issues.

Join the discussion. Leave a comment. Guest comments are welcome — add your email to get reply notifications.

No comments yet. Be the first to share your thoughts.

Anonymous · Startup Founder, BioPulse GmbH · 9 months ago

We use 8012, 240, and 4326 (release date) for our software, and haven't had any complaints from our notified body.

Join the discussion. Leave a comment. Guest comments are welcome — add your email to get reply notifications.

No comments yet. Be the first to share your thoughts.

Anonymous · Regulatory Affairs Consultant, NordicReg AB · 9 months ago

8012 is used to identify the software version and should be included as part of the UDI-PI.

Join the discussion. Leave a comment. Guest comments are welcome — add your email to get reply notifications.

No comments yet. Be the first to share your thoughts.

Want to add your answer to this question?
Write an answer under your name by logging in or signing up, or post anonymously.

Keep reading

All questions

How to convert GTIN-13 to GTIN-14 for EUDAMED UDI-DI submission?

Anonymous · 2 comments

4 months ago

EUDAMED appears to expect a GTIN-14 for UDI-DI, but most products have a GTIN-13 as default. Is it valid to add a leading zero to a GTIN-13 to create a GTIN-14 for EUDAMED? Should the check digit be r

Accepted 6 answers

The clinical development plan (CDP) required by MDR Annex XIV is meant to show how you plan to gather the necessary clinical evidence for your device.

Technical Documentation

Medical Device Translation: 3 Steps For Medical Device Software

Updated over 1 year ago

Sven Piechottka

List of Regulatory Requirements

Sören Hornof

updated about 2 years ago

Still have a question? Ask a question here publicly — for free.

Or talk to one of our consultants — first calls are free. Check out our services and prices.

Looking to automate your regulatory work? Check out our eQMS, Formwork. Built for lean, founder-led companies. There’s a free version too.