English中文(简体)FrançaisEspañolالعربيةРусскийPortuguês

+86 0769 88380789

English
English中文(简体)FrançaisEspañolالعربيةРусский

Contact Us

  • Guangdong Unique Flavor Co., Ltd.
    • +86 18929267983info@cuiguai.com
  • Room 701, Building C, No. 16, East 1st Road, Binyong Nange, Daojiao Town, Dongguan City, Guangdong Province

    • Get samples now

    Electronic Signature Compliance (21 CFR Part 11) in Production: A Practical Guide for E-Liquid Flavor Manufacturers

    Author: R&D Team, CUIGUAI Flavoring Published by: Guangdong Unique Flavor Co., Ltd. Last Updated: Nov 05, 2026 WhatsApp & Telegram: +86 189 2926 7983 Email: info@cuiguai.com   Electronic signature compliance stopped being a pharmaceutical-only conversation the moment flavor houses started holding regulated records for FDA-registered customers. A flavor concentrate is a food or tobacco-product input, but the batch record that produced it, the analytical worksheet that released it, and the change control that approved its specification are all company records that may be inspected by a regulator, a notified body, or a brand owner's quality auditor. When those records exist only as wet-ink initials on paper, a single misplaced binder can stall a customer qualification. When they exist in software without the right controls, a reviewer can quietly change a value and leave no trace. Both failure modes cost orders.   This guide explains what 21 CFR Part 11 actually asks for, how those requirements map onto the daily workflow of an e-liquid flavor manufacturer, and what a defensible implementation looks like when the company is not a drug manufacturer and does not intend to build a pharmaceutical-grade quality system. It is written for R&D managers, quality managers, and operations leads at flavor suppliers who are being asked Part 11 questions in supplier questionnaires and audits and need to answer them precisely rather than creatively.

    Why 21 CFR Part 11 Is Now a Flavor-Supplier Problem

    Part 11 is a short regulation. It sets the criteria under which the United States Food and Drug Administration will consider electronic records and electronic signatures to be trustworthy, reliable, and generally equivalent to paper records and handwritten signatures executed on paper. It does not create new recordkeeping obligations by itself. It attaches to records and signatures that other regulations, known as predicate rules, already require a firm to keep. That single design decision explains almost every practical question a flavor supplier asks about the rule, including whether it applies at all. For additional technical context on this point, see our tobacco flavor range.   Predicate rules reach flavor manufacturers through several doors. A facility that blends and ships flavor concentrates used in food is a food facility, and 21 CFR Part 117 records, including monitoring, corrective action, verification, and supplier approval documentation, are required records. A facility that supplies nicotine-containing e-liquid ingredients into the United States operates in the tobacco-product space, where the Federal Food, Drug, and Cosmetic Act as amended by the Tobacco Control Act imposes additional recordkeeping on those who manufacture, prepare, compound, or process tobacco products, including records supporting premarket submissions. Analytical results, stability data, and ingredient disclosures that support a customer's submission are therefore part of a regulated record set.   There is also a commercial driver that is stronger than either regulatory one. Brand owners conducting their own supplier audits increasingly issue a written questionnaire that asks, in plain language, whether the supplier's quality management system uses validated computerized systems with secure audit trails and unique electronic signatures. The question arrives even when the brand owner has no regulatory mandate to ask it, because the brand owner's own counsel has decided that demonstrating data integrity is the cheapest way to defend a future inspection. A supplier that answers no is placed on a remediation plan. A supplier that answers yes without evidence is worse off, because the follow-up audit will test the claim.
    A qualified operator reviews an electronic batch record with a secure time-stamped audit trail on a validated terminal in a flavor quality-control laboratory.

    Electronic Batch Records in a 21 CFR Part 11 Flavor Lab | CUIGUAI Flavor

    What Part 11 Actually Requires: The Core Provisions

    Scope: Predicate Rules and FDA's 2003 Guidance

    Under the agency's 2003 guidance on the scope and application of Part 11, FDA stated that it intends to enforce Part 11 with respect to records that are required by predicate rules and to electronic signatures that are required by predicate rules, and to exercise enforcement discretion for other records maintained electronically. That guidance is frequently misread as an exemption. It is not. The moment a firm chooses to rely on an electronic signature in place of a handwritten one for a required record, or the moment a customer or a certification scheme requires a signed electronic record, the discipline of Part 11 becomes the defensible standard. Most flavor houses therefore adopt Part 11 style controls voluntarily, and the rest of this article treats that voluntary adoption as the practical baseline.

    Section 11.10: Controls for Closed Systems

    Section 11.10 lists the controls that must be applied when records are managed on a closed system, meaning a system to which access is controlled by the people who are responsible for the content of the records. The list is compact but demanding: validation of systems to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records; the ability to generate accurate and complete copies of records in both human readable and electronic form suitable for inspection, review, and copying; protection of records to enable their accurate and ready retrieval throughout the records retention period; limiting system access to authorized individuals; use of secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions that create, modify, or delete records; use of operational system checks to enforce permitted sequencing of steps and events; use of authority checks to ensure that only authorized individuals can use the system, electronically sign a record, access the operation or computer system input or output device, alter a record, or perform the operation at hand; use of device checks to determine validity of the source of data input; determination that people who develop, maintain, or use electronic record systems have the education, training, and experience to perform their assigned tasks; and the establishment of, and adherence to, written policies that hold individuals accountable and responsible for actions initiated under their electronic signatures.   Three of those controls do most of the work during an inspection. The audit trail is the first: it must be computer-generated rather than operator-maintained, it must be time-stamped, and it must capture the who, the what, the when, and the previous value whenever a record is changed. The authority check is the second: a user must not be able to sign a step that their role does not permit, and the system, not a supervisor's memory, must enforce that boundary. The accurate copy is the third: when an inspector asks for the batch record, the firm must be able to produce a complete and readable copy that includes the audit trail if the inspector wants it, without a three-week data extraction project.

    Section 11.50: Signature Manifestations

    Section 11.50 requires that signed electronic records contain information associated with the signing that clearly indicates all of the following: the printed name of the signer; the date and time when the signature was executed; and the meaning, such as review, approval, responsibility, or authorship, associated with the signature. The requirement that the meaning be displayed is the one that flavor manufacturers most often miss. A system that records a generic approval click satisfies §11.50 only if the interface, the printed record, or the electronic view states whether the person was performing a technical review, granting a production release, or acknowledging that they authored the entry. Meaning has to be visible on the record, not inferred from which button was pressed.

    Section 11.70: Signature and Record Linking

    Section 11.70 states that electronic signatures and handwritten signatures executed to electronic records shall be linked to their respective electronic records to ensure that the signatures cannot be excised, copied, or otherwise transferred to falsify an electronic record by ordinary means. Practically, this means the signature cannot live in a separate spreadsheet, in an email thread, or in a scanned image pasted into a document. It must be bound to the record it signs, so that copying the signature away from the record breaks the record's integrity. Designs that store a signature block as editable text in the same Word file as the data satisfy nobody, because ordinary means of falsification include a copy and paste operation.

    Section 11.100 and Section 11.200: Identity and Signature Components

    Section 11.100 requires that each electronic signature be unique to one individual and not reused by, or reassigned to, anyone else, and that a person's identity be verified before the organization establishes, assigns, certifies, or otherwise sanctions an individual's electronic signature. Section 11.200 then sets out how the components work. An electronic signature that is not based on biometrics must employ at least two distinct components, such as an identification code and a password. When an individual executes a series of signings during a single continuous controlled session, the first signing must use all components and subsequent signings must use at least one component. Signatures must be used only by their genuine owners, and attempted use by anyone else must be reported to management. That last sentence is the basis of the shared-login prohibition that auditors test first.

    Section 11.300: Identification Codes and Passwords

    Section 11.300 governs the credentials themselves. Identification codes and passwords must be unique to each individual and never shared; they must be checked, recalled, or revised periodically to ensure they continue to function properly and that unauthorized use is detected and reported; loss management procedures must exist to de-authorize lost, stolen, missing, or otherwise potentially compromised tokens, cards, and other devices that carry or generate identification codes or passwords; transaction safeguards must be used to prevent unauthorized use of passwords and identification codes and to detect and report in an immediate and urgent manner any attempts at their unauthorized use; and initial and periodic testing of devices that bear or generate identification codes or passwords must be performed to ensure that they function properly and have not been altered. These clauses explain why password sharing, a common convenience in small production teams, is the finding that undermines every other control the firm has built.

    Mapping Electronic Signatures onto the Flavor Production Workflow

    Compliance becomes manageable when it is attached to specific decisions rather than to a system in the abstract. In a flavor plant, three decision points carry most of the regulatory weight: the release of a production batch, the disposition of a deviation or out-of-specification result, and the approval of a change to a specification or label. Each requires a signature with a clear meaning, and each requires the signature to bind to the record that the signer actually reviewed. For additional technical context on this point, see heavy metal testing of flavor extracts and the ICP-MS limits buyers now request.  

    Batch Record Review and Release

    A production batch record for a flavor concentrate includes the formula version, weighed quantities with tolerance checks, process parameters such as mixing time and temperature, in-process analytical results, packaging and labeling confirmation, and the final release decision. In a paper system, the reviewer initials each page and signs a summary sheet. In a compliant electronic system, the same reviewer opens a single review task, and the system presents the record plus its audit trail. The release signature must carry the meaning that the reviewer verified completeness and conformity, not merely that a screen was dismissed. If the reviewer changes a value during review, the audit trail must record the previous value, the new value, the reviewer's identity, and the reason, and the change must not erase the original entry.   The signature must also come from a person whose role authorizes release. A system in which any user with a login can release a batch fails the authority check even if every other control is perfect. Role definitions should be written down outside the software and then configured inside it, so that a role change in the organization triggers a deliberate change in the system rather than a permission edit performed quietly by an administrator.

    Deviations, Rework and Out-of-Specification Events

    Deviations are where electronic signature discipline earns its keep. A viscosity result outside the specification window, a mixing time that was shortened to protect a heat-sensitive top note, or a flavor that failed a sensory re-check all require a documented decision. The sequence matters: the person who raised the deviation should not be the only person who closes it, quality must record a disposition, and any rework instruction must be approved before it is executed. A compliant workflow enforces that sequence with operational checks, so the system will not accept a closing signature before the investigation section is complete.   The audit trail is the inspection target here. Inspectors do not read deviations to enjoy the narrative; they read them to confirm that the record reflects what actually happened. A deviation record whose audit trail shows that the disposition text was edited after the closing signature was applied will raise a data integrity question that no policy statement can answer. Designing the workflow so that later corrections are appended as amendments, with their own signature and meaning, is far cheaper than defending a retrospective edit.

    Specification and Label Change Control

    Flavor specifications change for good reasons and bad ones. A raw material supplier reformulates a botanical extract, a customer asks for a lower cooling intensity, a regulatory body restricts a substance, or analytical capability improves and the limit must be tightened. Each of those triggers a change control record that should follow a defined path: request, impact assessment covering affected customers and open orders, analytical justification, approval, effective date, and notification. Electronic signatures compress the cycle time of that path without weakening it, provided the approval signature is bound to the specific version of the specification being approved and the previous version remains retrievable.
    Secure, climate-controlled infrastructure supporting immutable audit trails and long-term record retention inside a compliant flavor manufacturing facility.

    Data Integrity, Audit Trails and Record Retention for Flavor Manufacturers | CUIGUAI Flavor

    Selecting and Validating a Compliant System in a Flavor Plant

    Validation Strategy and Risk Assessment

    Section 11.10 requires validation, and flavor houses frequently overcorrect by attempting a full pharmaceutical qualification package. A proportionate approach starts with a written statement of intended use, a risk assessment that identifies which records are regulated and which decisions are safety or legality relevant, and a verification plan whose depth follows that risk. Vendor documentation, including a software development lifecycle summary, a security whitepaper, and a customer validation kit, can carry part of the burden for commercial software, but the firm must still document its own configuration, its own role model, its own interfaces to instruments, and its own user acceptance testing against the specific workflows it operates.   Configuration is where most real risk hides. A laboratory information management system bought from a reputable vendor and then configured so that any analyst can edit any result has an unvalidated configuration, not an unvalidated product. The verification record should therefore capture the settings that carry regulatory meaning: audit trail enablement and immutability, password policy, session timeout, signature meaning definitions, approval routing rules, and the identity of the person authorized to change each setting. Those settings should also be change-controlled after go-live.

    Audit Trails, Time Stamps and Clock Control

    An audit trail is only as good as the clock that stamps it. If individual workstations, instruments, and servers are permitted to drift, a reviewer can create a plausible but false timeline. The practical control is to synchronize all systems to a single time source, restrict the ability to change system time to a small number of administrators, and record time changes themselves in the audit trail. The audit trail should also be non-editable by ordinary users, stored with the record rather than only in a separate log database, retained for at least as long as the record itself, and exportable in a format that a reviewer can read without specialist software.   Retention deserves an explicit decision. Flavor houses typically retain batch records far longer than the minimum, because reformulation cycles are long and a customer may return years later with a sensory complaint. If the electronic system retains the record but the audit trail is purged by a housekeeping job after twenty-four months, the firm has retained the conclusion and discarded the evidence. Retention rules for the record and its audit trail should be identical and should be documented in the same policy.

    Roles, Training and the Human Layer of Compliance

    Three Roles, Three Sets of Rights

    A workable role model for a mid-sized flavor manufacturer separates system administration from data entry and from approval. Administrators create accounts, assign roles, and manage configuration, but they should not be able to sign regulated records on behalf of production or quality. Analysts and operators create and review data within their assigned scope. Approvers release batches, close deviations, and authorize specification changes. Where the same individual must hold two of these roles, the combination should be documented, justified by staffing reality, and reviewed, rather than left ambiguous. Inspectors accept small organizations; they do not accept undocumented conflicts. For additional technical context on this point, see our cool flavor series.

    Training Evidence That Survives an Audit

    Section 11.10 requires that people who develop, maintain, or use electronic record systems have the education, training, and experience to perform their assigned tasks. A signed attendance sheet for a one-hour session is weak evidence. Stronger evidence links each named user to the specific procedures and system functions relevant to their role, records the date and the version of the procedure covered, and captures the user's acknowledgement of the policy that their electronic signature is the legally binding equivalent of their handwritten signature. Where the company relies on electronic signatures, a written confirmation of that equivalence should exist at the organizational level and be available for inspection. Re-training triggers should be defined for role changes, major system releases, and repeat data integrity errors.   Training also has to cover the uncomfortable cases. If an operator shares credentials because a shift handover is rushed, the policy has failed in practice regardless of what it says in writing. Fixing that usually requires a process change, such as a fast re-authentication path or a physical workstation at the point of use, rather than another reminder email.

    Common Inspection Findings and How to Prevent Them

    Findings We See Most Often

    The first cluster of findings concerns shared or generic accounts. An account named for a shift, a department, or a job title cannot produce a signature that is unique to one individual, and every record signed under it becomes questionable. The second cluster concerns audit trails that exist but are not reviewed; a trail nobody reads cannot detect the error or the tampering it was designed to expose. The third cluster concerns copies: the firm can print the record but cannot produce a complete electronic copy including the trail, or produces a PDF that omits the change history. The fourth cluster concerns the mismatch between the written procedure and the configured system, such as a procedure that requires dual approval while the software permits a single signature.   Prevention is unglamorous. Review audit trails on a defined schedule and keep a record of that review. Rehearse the inspection request, asking a colleague to demand a complete electronic copy of a batch record from two years ago and time how long it takes to produce. Reconcile the procedure list against the configured workflows once a year. Confirm that deactivated accounts are genuinely deactivated, because an employee who left the company should not be able to appear as a signer on a future record.   One further finding deserves mention because it is cultural rather than technical. Firms sometimes maintain an informal parallel record, such as a spreadsheet that operators use because the validated system is slow, and then transcribe results into the validated system afterwards. The informal record is now the source of truth and the validated system is a transcript. Replacing the spreadsheet with a faster, still validated entry path is the only durable correction.
    A line operator signs a production step at an industrial terminal, illustrating unique credential use and authority checks on the production floor.

    Electronic Signature Capture on an E-Liquid Filling Line | CUIGUAI Flavor

    A Ninety-Day Implementation Roadmap

    Days one to thirty focus on inventory and policy. List every electronic record that supports a regulated decision, including laboratory data, batch records, deviation reports, change controls, supplier approvals, and customer complaint investigations. For each one, state whether a signature is required, what the signature means, and who may apply it. Draft the organizational policy that establishes electronic signatures as the equivalent of handwritten signatures, the credential lifecycle rules, and the consequence framework for misuse. Those thirty days cost little and prevent expensive rework later.   Days thirty-one to sixty focus on the system and the roles. Confirm that audit trails are enabled, immutable, time-stamped, and retained with the records. Configure the role model, remove shared accounts, set password and session policies, and synchronize clocks. Complete the risk assessment and the verification plan, and begin executing the verification with real workflows rather than demonstration data. Configure report templates so that a complete electronic copy, including the audit trail, can be produced on request.   Days sixty-one to ninety focus on the people and the proof. Train each user against the procedures and functions that apply to their role, and record that training against named individuals. Run a full traceability exercise on three recent batches, covering the original data, the signatures, the audit trail, and the released certificate. Then run the inspection rehearsal and fix whatever it exposes. Finish by writing a short summary that states what the system covers, what it does not cover, and what compensating controls apply to the gaps, because a supplier that understands its own boundaries is far more credible than one that claims complete coverage.
    Quality reviewers apply a single meaning-carrying electronic signature to a production record, demonstrating the review and approval controls required by section 11.50.

    Dual Review and Signature Meaning Under 21 CFR Part 11 | CUIGUAI Flavor

    Frequently Asked Questions for Flavor Manufacturers

    Does Part 11 apply to us if we only make flavor concentrates and never make a finished tobacco product? Part 11 does not create obligations on its own. It applies to records that a predicate rule requires you to keep and to signatures that a predicate rule requires. Flavor houses usually adopt Part 11 style controls because 21 CFR Part 117 supplier approval records, customer audit demands, and destination-market requirements make the controls commercially necessary even when they are not textually mandatory for every record type. Document your reasoning either way.   Can we keep a paper master record and store a scan of it electronically? A scanned image is a copy, not an electronic record with a signature. If your handwritten signature is executed on paper, the paper record is the signed record and should be retained. If you intend the electronic copy to serve as the record, you need the controls in sections 11.10, 11.50, and 11.70 to apply to that copy, which a flat scan cannot provide. For additional technical context on this point, see UFI codes and European poison centre notification. Is a digital certificate or a biometric signature required? No. Section 11.200 allows a non-biometric signature built from at least two distinct components, such as an identification code plus a password. Digital certificates and biometrics are permitted options, not mandatory ones, and many flavor houses achieve compliance with a well-configured credential model and disciplined role management.   How long must we retain the audit trail? For as long as the record it belongs to is retained. If batch records are kept for ten years, the associated audit trails should be retained for ten years and be retrievable. Retention periods should be stated in the record retention policy and enforced by the system rather than left to a manual cleanup habit.   What do we do about a legacy paper archive? Do not attempt to retroactively sign historical paper records. Instead, define a cutover date, state in the policy which records are electronic from that date forward, and ensure the archived paper is indexed and retrievable. Inspectors accepted paper for decades and accept a documented cutover, but they do not accept a cutover date that moves backwards when new records need to be created.   Can a single person hold both an analyst role and an approval role? In a small organization, yes, provided the combination is documented, justified, and monitored, and provided the signature meaning distinguishes the two acts. Self-approval of a deviation that the same person raised is the case most likely to draw criticism and is worth avoiding even where staffing is thin.   How does European legislation interact with Part 11? European good manufacturing practice expectations for computerized systems, together with EU data integrity guidance, impose broadly similar requirements around audit trails, access control, and record integrity. A flavor house that supplies customers in both markets can usually satisfy both frameworks with one well-designed system and a mapping document that shows which control addresses which clause in each framework.

    Conclusion: Treat Electronic Signatures as a Product Requirement

    Electronic signature compliance is not a software purchase and it is not a documentation exercise. It is a design decision about how a flavor company records the judgments that make its products safe, consistent, and legal. The firms that get this right tend to be unremarkable in the best way: their batch records release without a chase, their audit trails answer questions instead of raising them, and their suppliers and customers can see exactly who approved what and when. That reliability shows up in commercial outcomes, because it removes an entire category of delay from customer qualification.   For a flavor manufacturer, the practical sequence is to decide which records are regulated or safety-relevant, decide which of them require a signature and what that signature means, configure a system that enforces those decisions with unique credentials and an unbroken audit trail, and then prove it through training and rehearsal. For additional technical context on ingredient documentation that customers commonly ask for alongside record control, our team discusses analytical expectations such as heavy metal testing of flavor extracts and the ICP-MS limits buyers now request, and the labeling and record obligations behind UFI codes and European poison centre notification. Our tobacco flavor range and our cool flavor series are supplied with the batch documentation, certificates, and specification history that these compliance programs depend on.  

    Request Samples and Technical Support

    Technical exchange/Free samples: 📞 Phone: +86 0769 8838 0789 🌐 Website: https://www.cuiguai.com 📧 Email: info@cuiguai.com 💬 WhatsApp & Telegram: +86 189 2926 7983

    References

    U.S. Food and Drug Administration. 21 CFR Part 11, Electronic Records; Electronic Signatures. https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11   U.S. Food and Drug Administration. Guidance for Industry: Part 11, Electronic Records; Electronic Signatures - Scope and Application (2003). https://www.fda.gov/regulatory-information/search-fda-guidance-documents/part-11-electronic-records-electronic-signatures-scope-and-application   Pharmaceutical Inspection Co-operation Scheme. Good Practices for Data Management and Integrity in Regulated GMP/GDP Environments, PI 041-1. https://picscheme.org/   International Council for Harmonisation. ICH Q7, Good Manufacturing Practice Guide for Active Pharmaceutical Ingredients. https://www.ich.org/page/quality-guidelines
    For a long time, the company has been committed to helping customers improve product grades and flavor quality, reduce production costs, and customize samples to meet the production and processing needs of different food industries.

    QUICK LINKS

    PRODUCTS

    Friendship link

    CONTACT  US

  • Guangdong Unique Flavor Co., Ltd.
    • telegram +86 189 2926 7983info@cuiguai.com
  • Room 701, Building C, No. 16, East 1st Road, Binyong Nange, Daojiao Town, Dongguan City, Guangdong Province

    • ABOUT  US

    The business scope includes licensed projects: food additive production. General projects: sales of food additives; manufacturing of daily chemical products; sales of daily chemical products; technical services, technology development, technical consultation, technology exchange, technology transfer, and technology promotion; biological feed research and development; industrial enzyme preparation research and development; cosmetics wholesale; domestic trading agency; sales of sanitary products and disposable medical supplies; retail of kitchenware, sanitary ware and daily sundries; sales of daily necessities; food sales (only sales of pre-packaged food).

    Send Inquiry
    WhatsApp

    Request Inquery