Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2937
NATO nations and NATO bodies implementing the ration requirements this agreement covers
STANAG 2937 is NATO's ratified agreement covering AMedP-1.11 and AMedP-1.18, the publications setting requirements for individual and group operational rations.
STANAG 2937 is the NATO standardization agreement covering operational rations for military use. Like every STANAG, it is not itself a technical specification: it is the agreement by which NATO nations commit to implementing one, and the actual ration requirements live in the two Allied Publications it covers, AMedP-1.11 and AMedP-1.18.
Participating nations agree to implement AMedP-1.11, Edition C, and AMedP-1.18, Edition B. The cover itself sets no ration requirement beyond that commitment. Its stated aim is to improve interoperability of NATO military forces by standardizing the minimal characteristics and quality assurance of operational rations and providing guidance for supplying them, and to enhance the exchange of rations among NATO nations.
This is Edition 6, promulgated 18 June 2025, superseding Edition 5 of 25 April 2019. The changes respond to nations' 2019 ratification feedback and revise the nutritional and acceptance chapters of both covered publications.
A STANAG binds a nation once ratified, and this one is effective on receipt for participating nations and NATO bodies. National ratification responses are recorded in NATO's Standardization Documents Database, and allies report both ratification and implementation details through NATO's electronic reporting tool; partner nations are invited to do the same. Participating nations agree that rations used to supply partner nations in multinational operations will conform to the characteristics described in AMedP-1.11 and AMedP-1.18.
None of that reaches a ration manufacturer directly. A supplier meets STANAG 2937 only once a national or NATO tender writes AMedP-1.11's or AMedP-1.18's requirements into the contract - the cover has nothing for a supplier to act on before that point.
The STANAG is reviewed in accordance with AAP-03, with the result recorded in the NSDD. It is published by the NATO Standardization Office (NSO), which also receives comments on it, and is supervised by NATO's medical standardization committees (COMEDS, MCMedSB, MedStd, FHP, FWSVS P).
The cover also names further documents a nation may need alongside its rations agreement, cited as related reading rather than as binding requirements of this STANAG: STANAG 2034 (mutual logistic assistance procedures), STANAG 3113 (support to visiting personnel, aircraft and vehicles), STANAG 2556 (food safety, defence and production, covering AMedP-4.5, AMedP-4.6, AMedP-4.7, AMedP-4.12 and AMedP-4.14), STANAG 2136 (water quality during operations, covering AMedP-4.9), STANAG 2629 (water production, storage and distribution, covering ATP-104), and four environmental-testing STANAGs: STANAG 4370 (covering AECTP-100 and AECTP-600), STANAG 4866 (covering AECTP-230 and AECTP-300), STANAG 4867 (covering AECTP-240 and AECTP-400) and STANAG 4868 (covering AECTP-250 and AECTP-500).
Nobody is certified against STANAG 2937. It is a ratification and implementation agreement between nations, and its only stated check is administrative: ratification and implementation responses recorded in the NSDD, and a periodic review of the STANAG itself under AAP-03. Where a national tender asks a ration manufacturer for a management-system or food-safety certificate, that certificate is held against the scheme that issues it, not against this STANAG. The specifications a ration is actually assessed against, and the audits a manufacturer may face, sit in AMedP-1.11 and AMedP-1.18.
This agreement is between nations; nothing in it is implemented on a factory floor. Where a national tender writes AMedP-1.11's or AMedP-1.18's ration requirements into a contract, a manufacturer's own work is producing to those specifications and evidencing that it did: batch records, ingredient and supplier traceability, the certificate the tender asks for, and the corrective actions raised when something falls short.
ComplyTrain gives a supplier a controlled place to hold that documentation - procedures, training records, internal audits, and the evidence trail an auditor asks to see - version-controlled and ready to produce. It does not certify anyone against AMedP-1.11, AMedP-1.18 or any other scheme, does not help a supplier win a ration contract or pass an inspection, and does not carry out the ration production, testing or physical inspection itself. The certificate stays the manufacturer's to earn.
Which tier applies to a given contract, and which related documents come with it, is set by the contract and the customer's quality clause. The standards explorer shows what else sits alongside a ration contract - talk to us about how ComplyTrain can hold the evidence trail that work produces.
Tell us how you need to work with STANAG 2937 and what you need from it. We will come back to you about what ComplyTrain can do.
Thank you. Your list is on its way to your inbox, and we will come back to you on what working with these standards in ComplyTrain involves, usually within one business day.
Only through ratification and a contract. A STANAG binds a nation once that nation has ratified and implemented it, and it reaches a supplier when a tender or contract writes AMedP-1.11's or AMedP-1.18's requirements into its terms, not by existing on its own.
STANAG 2937 is the agreement between nations to implement the two publications; it carries no ration requirements of its own. AMedP-1.11 and AMedP-1.18 are the technical publications that set the actual requirements for individual and group operational rations.
No. STANAG 2937 names no certification, notified-body or audit scheme, for a nation or for a supplier. Any certificate a ration manufacturer holds, such as ISO 9001 or ISO 22000, is assessed against that scheme, not against this agreement.
Edition 6, promulgated 18 June 2025, supersedes Edition 5 of 25 April 2019. It responds to nations' 2019 ratification feedback with revisions to the nutritional and acceptance chapters of both covered publications.
One system for the whole compliance programme. Start with the module you need most.
Collect information the same way every time, and decide in advance what happens next.
Know whether your controls are operating, not just whether a policy says they exist.
Turn the compliance work you already know about into a plan with owners, dependencies and dates.
Know what you can offer, and hold the evidence behind every configuration you offer it in.
Eight built-in reports across every module, scheduled, delivered, and filed where the evidence lives.
The sector news that matters to your organisation - read and rated by AI, and delivered as a scheduled digest in your own language.
AI reads the tender pack and pulls out the requirements, deadlines and rules - then helps you draft the response from your own approved content, with you reviewing every step.
One current register of the suppliers and partners you depend on - each risk-assessed, re-assessing itself on schedule, and wired straight into your risk register.
See every requirement you face - across every standard, plus your own contracts and policies - traced to the documents, evidence and processes that satisfy it.
Identify, score, treat and review your risks in one place - with AI to help anyone run a proper assessment, and a defensible trail behind every decision.
Assign training, prove it was understood, and hold the competence records an auditor asks for.
Draft compliance documents with AI, keep every version under control, and export them beautifully branded - all in one place.
Audits, corrective actions, processes and approvals in one quality system, organised around ISO 9001.
Medical device manufacturers operate under more regulatory pressure than almost any other sector outside pharmaceuticals. The rules govern how you design a device, how you make it, how you track it after it ships, and how you respond when something goes wrong.
Learn how EU dual-use export controls apply to encryption, sensors, and software, how classification works under Annex I, and why sending source code by email can count as an export.
A practical way to turn in-your-head risk management into a register that survives staff turnover and answers the risk questions now showing up in tenders.