Write the complete requested identity
Terminal modifications are part of the requested product identity. Indicate the required N-terminal and C-terminal forms in the project brief, together with the sequence notation and any other modification sites. Use a consistent notation and explain abbreviations that could be read in more than one way.
Ask questions before treating a request as feasible
- Is the requested terminal form unambiguous?
- Are there other modifications or conjugation requirements that must be considered with it?
- What identity information and analytical records are requested at delivery?
- Are acceptable alternatives explicitly permitted?
Do not infer a supplier’s full capability from examples
Published examples of modifications describe possible service categories, not universal availability for every sequence. Ask for project-specific confirmation. If an alternative terminal form is proposed, record it as a change requiring approval rather than an invisible substitution.
Keep the approved notation with the order
Use the same identity wording in the technical brief, quotation and document review. The comparison should be against the approved version, not an early email attachment.
For general examples of modification terminology, see GenScript’s modification reference. That source describes its own services and does not establish ApexPep’s capability or availability.