Sample write up for interpretation of production code.

Hi all,

Im looking for sample of interpretation of production code write up. Thanks in advance

new to this form hello

Like a lot coding system?  I put something like this on the bottom of my specification sheets -

ABBBCD-EE

A = Line

B = Julian Date

C = Last digit of the year

D=Shift

E = Operator

Or "Date Code = DD/MM/YY"  Day/Month/Year





:welcome: Paraguard!

Jeez you're awake MM I hadn't a clue what carine was looking for......  :oops2:

Those all work. We also have Enjoy by July 12, 2015.  Today's date plus shelf life.

We had some write-up at my last position that was something to the effect of:

At *Company Name* our production lot identification system is a serialized number that identifies the line the product was produced on and the date it was produced.  Please see an example of the production code below.

Then we had the example much like MM's code above.

We also had a Best By date while the company we co-packed for required us to use a Use By date.  The difference is that if it's a product someone can get sick using after the shelf life they didn't want to suggest the date and have someone use it after that date therefor they were telling the consumer to use it by XX/XX/XXXX rather than implying "Meh it's ok if you eat this yogurt when it's a year past the shelf life".

Carine,

Is this your product or are you packing for someone?

We are majorly a co-packer so most of our coding comes directly from the customers specifications. Some include a code for the processor the product was ran through, state tax codes where applicable (USA - Connecticut), others require Julian dates, Some require Use by or Best By or "For best quality use by" (this last one is a good one for products that may not essentially have an actual shelf life, but more of a recommended one- like Mr. I was talking about)

If this is your own product, Make sure any regulatory requirements are addressed (if applicable) and just ensure that your system of coding makes sense for what you are doing. If you track records by production date - then you will more than likely want to code product this way. If you are a bulk batcher and tracking by product lot makes more sense, then integrate that into your coding system. Start with whatever you hinge production related paperwork on.

Now I could start a rant about Best before dates........

I tried pitching putting "Best before", "Okay before", and "Don't eat after" dates on one of our new product lines, but marketing wouldn't bite.

I tried pitching putting "Best before", "Okay before", and "Don't eat after" dates on one of our new product lines, but marketing wouldn't bite.

In this order

still fresh by:

Wouldn't hurt to eat by:

Stale BUT still good by:

if you're a college student on a budget by:

if you have a death wish by:

wouldn't touch with a 10 foot pole by:

It's amazing the variety of versions that are out there. Pure English Please "You WILL get sick if you eat this after this date: XX/XX/XX" That outta work. But M_M is right, marketing won't "bite"...eh eh...anyone???

It's amazing the variety of versions that are out there. Pure English Please "You WILL get sick if you eat this after this date: XX/XX/XX" That outta work. But M_M is right, marketing won't "bite"...eh eh...anyone???

:cheezy:  

:cheezy:  

Why is it only I_R_I gets me??? The same with the 2 birds. Thanks I_R_I...I appreciate you understanding me

Why is it only I_R_I gets me??? The same with the 2 birds. Thanks I_R_I...I appreciate you understanding me

I have a huge space in my heart for Arnold. His one liner puns are the best.. but yours, RG3, definitely come in close second.