FDA can require the electronic sortable spreadsheet only when it needs your traceability records to prevent or mitigate a foodborne illness outbreak, to help carry out a recall, or to otherwise address a threat to public health. In those situations you must provide the requested information, for the foods and date ranges or traceability lot codes FDA names, within 24 hours of the request or within a longer time FDA agrees to. Smaller farms, retail food establishments, restaurants and other firms below sales thresholds in 21 CFR 1.1455(c)(3)(iii) may answer in another form, but not more slowly. During a routine inspection, FDA can ask for your records within 24 hours, but not for the spreadsheet.
The practical test is whether your systems can produce one clean file, grouped by critical tracking event, from records that live in an ERP, a WMS, a production system and a stack of shipping documents. This note covers the trigger, the exemptions, what goes in the file, the query path across systems and a rehearsal plan. This note is not legal advice. Whether the rule applies to you and which exemptions you qualify for are questions for your counsel and for FDA’s guidance.
Where enforcement stands in November 2026
FDA will not enforce the Food Traceability Rule before July 20, 2028, under a congressional directive. That is the accurate summary as of November 21, 2026.
According to FDA’s rule page (content current as of November 4, 2026), the original compliance date was January 20, 2026. FDA then proposed a 30-month extension to July 20, 2028, published August 7, 2025. After that, the Continuing Appropriations, Agriculture, Legislative Branch, Military Construction and Veterans Affairs, and Extensions Act, 2026 directed FDA not to enforce the rule before the same date, and FDA says it intends to comply.
A Federal Register search on November 21, 2026 found no final rule completing the proposed extension, and 21 CFR 1.1455, quoted below from the eCFR, has not been amended since the rule took effect in January 2023. When FDA preamble text is quoted here, it comes from the 2022 final rule (87 FR 70910). The extra time is useful for one thing above all: building and rehearsing the export before anyone needs it.
Two different 24-hour requests in 21 CFR 1.1455
Section 1.1455 contains two separate record requests with the same 24-hour clock. Paragraph (c)(1) is the everyday request. Paragraph (c)(3) is the emergency request, and only it carries the spreadsheet. Reading them as one leads to the wrong conclusion that every FDA records request needs the spreadsheet.
| Everyday request: 1.1455(c)(1) | Emergency request: 1.1455(c)(3) | |
|---|---|---|
| When FDA can make it | Any time an authorized FDA representative asks for the records required by the subpart | When necessary to prevent or mitigate a foodborne illness outbreak, assist in a recall, or otherwise address a threat to the public health |
| What you provide | All records required under the subpart, as kept (paper, electronic or true copies) | The information you must keep under the subpart “for the foods and date ranges or traceability lot codes specified in the request” |
| Deadline | Within 24 hours, or a reasonable time FDA has agreed to | Within 24 hours of the request, including a phone request, or a reasonable time FDA has agreed to |
| Form | Your records, plus “any information needed to understand these records” | An electronic sortable spreadsheet for CTE records under 1.1325 to 1.1350, unless an exemption in (c)(3)(iii) or (iv) applies |
| Typical setting | Routine inspection | Outbreak investigation, recall, other public health threat |
The final rule’s preamble removes any doubt about routine inspections. FDA wrote: “During a routine inspection that does not meet the conditions described in Sec. 1.1455(c)(3), a covered entity would not be required to provide FDA with an electronic sortable spreadsheet.” It also called the spreadsheet “not a routine record.”
Both requests share one requirement that is easy to underrate. Under (c)(1), you must supply the information needed to understand your records, “such as internal or external coding systems, glossaries, abbreviations, and a description of how the records you provide correspond to the information required under this subpart.” Under (c)(3)(ii), the spreadsheet must come “along with any other information needed to understand the information in the spreadsheet.” Either way, a file full of internal site codes and item numbers is not a complete answer.
What triggers a spreadsheet request
The trigger is the purpose of FDA’s request, not its urgency or its source. Under 1.1455(c)(3), the emergency request applies “when necessary to help FDA prevent or mitigate a foodborne illness outbreak, or to assist in the implementation of a recall, or to otherwise address a threat to the public health.”
The rule gives one example of such a threat: situations where FDA has “a reasonable belief that an article of food… presents a threat of serious adverse health consequences or death to humans or animals” because it is adulterated under section 402 or misbranded under section 403(w) of the Federal Food, Drug, and Cosmetic Act. The words “including but not limited to” in the rule mean that list is not complete.
The preamble adds two limits on how FDA intends to use the power. FDA “will only request an electronic sortable spreadsheet when we conclude that obtaining the information in this format is necessary,” and “will only request information on the FTL foods that may be associated with the outbreak, recall, or other threat to public health.”
What FDA’s request will name
The request defines the scope of your query. The rule says it covers “the foods and date ranges or traceability lot codes specified in the request.” In the preamble (Response 473), FDA said it “will specify the particular FTL foods for which we need to review CTE/KDE records, focusing on particular dates on which the food was handled and/or particular traceability lot codes.”
That gives you the three inputs to design the export around:
- The food. FDA will describe a product, such as a commodity or a product name. You have to translate that into your item numbers, which is why a Food Traceability List flag in the item master matters.
- A date range. Dates on which the food was handled at your sites, which may mean receipt dates, production dates or ship dates.
- Traceability lot codes. Sometimes FDA will name specific lots, which you then need to find in your records with their TLC source.
Phone requests and the clock
The clock starts when FDA asks, even by phone. Under 1.1455(c)(3)(i), if the request is made by phone, FDA will also put it in writing on your request, “however, you must provide the requested information within 24 hours (or within some reasonable time to which FDA has agreed) of the phone request.” The preamble confirms that this applies even to firms that are exempt from the spreadsheet format.
The 24 hours is not absolute. In the preamble (Response 470), FDA said it “may be reasonable for FDA to extend the 24-hour timeframe” in some circumstances, for example for a large request to a firm that keeps paper records. Treat that as something to agree with the FDA representative at the start, in writing, not as a fallback after hour 20.
Who may answer in another form
Under 21 CFR 1.1455(c)(3)(iii), three groups may provide the requested information “in a form other than an electronic sortable spreadsheet.” The thresholds are three-year averages on a rolling basis, “adjusted for inflation using 2020 as the baseline year.”
| Group | Threshold in the rule (before inflation adjustment) | What is measured |
|---|---|---|
| Farms | No more than $250,000 | Average annual sales of raw agricultural commodities, plus the market value of raw agricultural commodities manufactured, processed, packed or held without sale (for example, held for a fee), over the previous 3 years |
| Retail food establishments and restaurants | No more than $1 million | Average annual monetary value of food sold or provided over the previous 3 years |
| Any other person (manufacturers, processors, distributors, 3PLs and so on) | No more than $1 million | Average annual sales of food, plus the market value of food manufactured, processed, packed or held without sale (for example, held for a fee), over the previous 3 years |
A fourth route is narrow: under 1.1455(c)(3)(iv), FDA “will withdraw a request for an electronic sortable spreadsheet… as appropriate, to accommodate a religious belief of a person asked to provide such a spreadsheet.”
These are not the same as the rule’s full exemptions in 21 CFR 1.1305. For example, a retail food establishment or restaurant with average annual food sales of no more than $250,000 is outside the rule entirely under 1.1305(i). One between $250,000 and $1 million is inside the rule but exempt from the spreadsheet format. Both figures are inflation-adjusted from 2020.
How the thresholds are measured for 3PLs and distributors
The third group’s test counts more than revenue. It adds “the market value of food they manufacture, process, pack, or hold without sale (e.g., held for a fee).” A 3PL that earns modest storage fees but holds client inventory of high market value can therefore exceed $1 million. A distributor counts its food sales.
Example (fictional). Tallgrass Cold Storage is a small 3PL. Its storage and handling fees average $600,000 a year, and it sells no food. Over the last three years it held client food with an average market value of $4.2 million a year. Its finance lead first assumed the firm was under the $1 million line because its own revenue is. Read against 1.1455(c)(3)(iii)(C), the measure is sales of food plus the market value of food held without sale, so the relevant figure is about $4.2 million, well above the threshold before any inflation adjustment. The firm plans on producing the spreadsheet, and asks counsel to confirm the reading.
Exempt from the format, not from the clock
An exempt firm still has to answer within 24 hours, or within a time FDA agrees to. The preamble says such entities “must provide the information in a different form, such as paper records or electronic records that are not compiled in a sortable spreadsheet.” The records still have to be findable by food, date range and lot code. Small size buys you a different file format, not a different deadline.
Two practical points follow. First, for a firm with electronic records, producing a sortable file may still be the fastest way to answer within the deadline, exempt or not. Second, customers set their own expectations. Walmart’s published Food Traceability KDE Requirements sheet, for example, lists “ASN via EDI (or) EPCIS via API” as the ways to send traceability data, with no size-based exception on the sheet. Being exempt from the spreadsheet format under the rule does not change what a buyer can require in a supply agreement.
What goes in the spreadsheet
The spreadsheet carries the information you are required to keep under 21 CFR 1.1325 through 1.1350: the key data elements (KDEs) for each critical tracking event (CTE) you perform, such as receiving, transformation and shipping. It covers only the foods, dates or lot codes in FDA’s request, plus whatever FDA needs to understand the content.
FDA has published a template in Excel and a version with sample data, with PDF copies of each. FDA’s page is clear that the template is optional: “This template is presented for illustrative purposes. You are not required to use this specific electronic sortable spreadsheet template to comply with the rule.” The preamble said the same in 2022: FDA did not intend to issue an “official” template that all firms must use.
Even so, the template is a useful map of how FDA lays out the KDEs. Opened in November 2026, the Excel file has an introduction tab, a definitions tab and 13 tabs for events and situations, including Shipping, Receiving, Receiving From Exempt and Transformation. FDA’s notes say you only complete the tabs for the events you performed that relate to the request.
Which tabs you will fill
The 13 event tabs in the template are Harvesting, Cooling, Initial Packing, Initial Packing Sprouts, Initial Packing from Exempt, First Land-Based Receiving, Shipping, Receiving, Receiving From Exempt, Transformation, and three tabs for purchases by retail food establishments, restaurants and farm to school programs. A business in the middle of the supply chain may touch three or four of them. The tabs follow the events you perform, not your industry label, so map your own events first.
| Business | Events it typically performs for listed foods | Template tabs likely in a response |
|---|---|---|
| Distributor or wholesaler | Receiving, shipping, receipt from suppliers the rule does not apply to | Receiving, Receiving From Exempt, Shipping |
| 3PL holding client inventory | Receiving and shipping at its warehouses | Receiving, Shipping |
| Fresh-cut processor or manufacturer | Receiving, transformation, shipping | Receiving, Transformation, Shipping |
| Packinghouse | Initial packing, including product from farms the rule does not apply to, then shipping | Initial Packing, Initial Packing from Exempt, Shipping |
| Repacker or relabeler | Receiving, transformation (repacking and relabeling count), shipping | Receiving, Transformation, Shipping |
How the template breaks fields apart
Three details in the template matter for anyone writing the export query:
- Location descriptions are split into seven columns. Business name, phone number, street address or geographic coordinates, city, state or region, ZIP or postal code, and country. On the Shipping and Receiving tabs, three location descriptions make up 21 of the 36 columns.
- Product descriptions are split into six columns. Product name, brand name, commodity, variety, packaging size and packaging style, matching the 1.1310 definition of product description.
- Dates are labeled mm/dd/yyyy, and there is room for a second reference document type and number on each event.
The sample-data version shows two more conventions. On the Transformation tab, each input lot gets its own row, and the output lot’s details repeat on every row. In several sample rows, the TLC source reference is given as a web address in the GS1 Digital Link style, or as an FDA Food Facility Registration Number, and the location columns are filled with “n/a (See Traceability Lot Code Source Reference).”
The context file
The rule’s phrase “any other information needed to understand the information in the spreadsheet” deserves its own deliverable. A short glossary sheet or document should list internal codes that appear in the file (site codes, unit of measure abbreviations, reference document prefixes), explain how your records map to the KDEs, and name a contact. Your traceability plan already has to identify “a point of contact for questions regarding your traceability plan and records” under 21 CFR 1.1315(a)(4).
Where each column comes from: the query path across systems
The spreadsheet is a join across systems that were never designed to be joined in a hurry. The rule allows that: 1.1455(g) says you do not have to keep everything “in a single set of records,” as long as your traceability plan says where each record is. The cost of that freedom is paid on the day of the request, unless the query path is built in advance.
| Spreadsheet content | Usual system of record | What to check |
|---|---|---|
| Food identification (FDA’s product description to your items) | ERP item master | A Food Traceability List flag on each item, with an effective date |
| Product description fields (name, brand, commodity, variety, pack size, pack style) | ERP or PIM item master | If pack size and style sit in free text, split them once, not on the day |
| Receiving events: TLC, TLC source, quantity, date, previous source | WMS receipts, EDI inbound ASNs | TLC stored exactly as received, with its source |
| Transformation events: inputs, outputs, quantities, completion date | Production module, MES or batch records | Input lots recorded as supplier TLCs, not only internal lots |
| Shipping events: TLC, quantity, date, recipient | WMS shipments, ERP sales orders and invoices | One line per item and TLC, not per item |
| Location descriptions (all parties) | ERP site, supplier and customer masters | Phone numbers and street addresses populated for every ship-to |
| Reference document type and number | WMS, ERP, TMS (bills of lading), document storage | A consistent numbering scheme that a person outside your company can read |
In its discussion of the definition of reference document number, the preamble notes that these numbers “might be used in an electronic sortable spreadsheet requested by FDA… to indicate the particular reference documents that contain information included in the spreadsheet.” That is why the bill of lading number from the TMS, or the ASN number from the EDI gateway, earns a column.
The query, step by step
Write the query as a procedure before you write it as code. Each step below is a place where a decision has to be made once, in calm conditions:
- Resolve the foods. Map FDA’s description to your item numbers using the Food Traceability List flag. The list also covers foods that contain a listed food as an ingredient, when the listed food “remains in the same form,” so include those items.
- Resolve the lots. If FDA named TLCs, find each one together with its TLC source. If FDA gave a date range, find every TLC of the in-scope items handled at the in-scope sites in that range.
- Pull the events. Receipts, transformations and shipments for those lots, filtered on the event date. Decide in advance which date field drives the filter for each event type.
- Follow transformations. Where a requested lot was an input, the transformation rows and the shipments of the output lots may be in scope. When unsure, confirm the scope with the FDA representative rather than guessing.
- Resolve locations. Replace every site, supplier and customer code with its seven location description fields.
- Attach reference documents. Add the document type and number that holds each event, such as the receipt number, ASN number, work order or bill of lading.
- Reconcile. Compare quantities per lot and event against inventory movements in the WMS and ERP, and explain every difference.
- Export and explain. Write the tabs, then generate the glossary from the codes that actually appear in the file.
The join keys that break
Join failures are as dangerous as missing data, because they produce a file that looks complete. Four are worth testing in advance:
- TLC without its source. A traceability lot code is unique only within the records of the place that assigned it. Joining receipts to shipments on the code alone can merge two suppliers’ lots. Our note on traceability lot codes covers how to store the code and its source together.
- Internal lot instead of TLC. If the WMS tracks an internal lot and the supplier’s code sits in a comment field, the shipping rows will carry the wrong identifier.
- Item number drift. If the ERP and WMS item numbers differ, or one item was renumbered during the date range, the food filter misses rows.
- Ship-to without a phone number. Location descriptions need a phone number, and customer masters built for invoicing may leave it blank.
Deciding which system owns each of these fields is a design question in its own right, covered in our note on choosing the system of record for each inventory field.
Location descriptions from master data
The location columns come from master data rather than transactions, so a better transaction query cannot fix them. Build a view, in advance, that turns every site, supplier and customer ship-to code into the seven location description fields. Then every event row only carries codes, and the export resolves them in one step. The TLC source columns are the exception: they come from what the supplier sent with each lot, stored at receipt.
If a supplier sends a TLC source reference instead of a location description, keep it as sent. FDA’s sample data shows a reference in the reference column and “n/a” text in the location columns. Do not try to look up the supplier’s packer yourself.
Making the file sortable
The rule does not define “sortable,” and the preamble says 1.1455(c)(3)(ii) “does not prescribe a specific technology for creating the sortable spreadsheet.” In Response 470, FDA added that “such spreadsheets can be created using software that is readily available and commonly used for other general business purposes.” What follows are practical rules that keep the file usable when someone at FDA sorts and filters it.
- One header row per tab, one event per row. No merged cells, titles above the header, blank spacer rows or subtotals. Each of these breaks sorting.
- One value per cell. A city and state in one cell cannot be filtered by state. The template’s split columns show the expected grain.
- Text identifiers stay text. TLCs, ZIP codes and reference numbers can have leading zeros. Format those columns as text and test whether opening the file in a spreadsheet program changes any of them.
- Consistent dates. Use one date format throughout. The template labels dates as mm/dd/yyyy.
- Units in their own column. Quantity and unit of measure are separate KDEs and separate columns.
- Explicit blanks. Where a field does not apply, say so consistently. FDA’s sample file uses “n/a” with a short reason.
The rule asks for completeness and accuracy, not volume. A long file that reconciles to the physical records is worth more than a fully populated one built on guesses.
Records the query has to reach
The export is only as complete as the records behind it, and several provisions of 21 CFR 1.1455 decide where those records can be and how long they must last. Each one turns into an IT requirement.
- Two years of history. Under 1.1455(d), you must keep the records “for 2 years from the date you created or obtained the records.” A request’s date range can reach back that far. If your WMS purges transaction detail or your ERP moves it to an archive, the query has to reach the archive too.
- Cloud and offsite systems. Under 1.1455(c)(2), offsite storage is allowed if records can be retrieved and provided onsite within 24 hours, and “electronic records are considered to be onsite if they are accessible from an onsite location.” A hosted WMS is fine, provided the people on the runbook can reach it.
- Links instead of copies. Under 1.1455(a)(1), electronic records “may include valid, working electronic links” to the required information. Scanned bills of lading linked to a receipt count, as long as the links still work.
- No duplicate records. Under 1.1455(f), you do not need to duplicate existing business records that already hold the information. You may supplement them instead.
- Part 11. Under 1.1455(e), electronic records kept to satisfy this subpart are exempt from FDA’s electronic records rule in part 11, but records also required by other regulations stay subject to part 11 unless otherwise exempt.
- Language. Under 1.1455(c)(4), you must provide an English translation of records kept in another language within a reasonable time after FDA asks. Foreign suppliers’ documents are the usual case.
Who does what in the first 24 hours
A request can arrive at any hour, the rule allows it to come by phone, and the person who answers may not be the person who can run the query. A written runbook, assigned to named roles, turns the 24 hours into a sequence of checkable steps. The timings below are an example plan, not a requirement; adjust them to your request volume and systems.
| Elapsed time (example plan) | Step | Owner |
|---|---|---|
| 0 to 1 hour | Log the request: who called, foods, date range or TLCs, contact details. Ask for it in writing under 1.1455(c)(3)(i). Agree the delivery method. | Traceability point of contact |
| 1 to 2 hours | Translate the foods into item numbers; confirm which sites and events are in scope | QA lead with item master owner |
| 2 to 6 hours | Run the staging query; produce draft Receiving, Transformation and Shipping tabs | IT or data lead |
| 6 to 10 hours | Reconcile row counts and quantities to WMS and ERP totals; investigate gaps | QA lead and warehouse lead |
| 10 to 14 hours | Fill gaps from paper or scanned documents; record what was filled by hand | QA team |
| 14 to 18 hours | Build the glossary and the mapping note; second-person review of the whole file | QA lead and a reviewer |
| 18 to 22 hours | Approve and send; keep a copy of exactly what was sent | Traceability point of contact |
| 22 to 24 hours | Buffer for questions and corrections | All |
Two points from FDA’s guidance shape the runbook. First, the request may be made “in-person or remotely (e.g., by phone),” and the clock starts then. Second, if another company keeps your records, FDA’s February 2026 draft Q&A guidance says it “may make sense for the third party to send the electronic sortable spreadsheet directly to FDA,” and that the logistics “can be discussed with the FDA representative.” You remain responsible under 1.1455(b). A 3PL agreement should say who runs the query, in what format, and how fast.
On delivery, the 2022 preamble said FDA was considering “a dedicated email box or through an online reporting mechanism, such as a web-based portal.” Confirm the current method with the FDA representative who makes the request.
Writing and maintaining this runbook is documentation work in its own right. It belongs next to the traceability plan and the SOPs your team already keeps, and it is the kind of procedure our documentation service writes and tests with the people who will use it.
Rehearsing with a mock request
The only reliable way to know your time to file is to measure it. Nothing in the rule requires a drill, and the preamble says firms are not required to prepare the spreadsheet daily or to duplicate records in advance. A drill is simply the cheapest way to find the broken joins before FDA does.
A rehearsal plan that tests the weak points named above:
- Pick a realistic scope without warning the team. One Food Traceability List item, a two-week date range, all sites that handled it. Alternate drills between a date-range request and a request for specific TLCs.
- Start the clock with a phone call to the traceability point of contact, outside normal hours at least once a year.
- Run the runbook as written. Do not let the most experienced person improvise; the point is to test the document.
- Score the output on five measures: hours to a sent file; share of rows reconciled to physical records; number of TLCs without a source; number of location descriptions missing a phone or street address; number of codes in the file not explained in the glossary.
- Trace one lot in both directions. Pick one shipped TLC and confirm you can name its receipt and, if transformed, its inputs.
- Write up the gaps as defects with owners and dates, and retest them in the next drill.
Example (fictional). Prairie Fresh Distribution runs its first mock request on a Tuesday evening: all fresh cucumbers (item EX-31207) handled at two sites between June 2 and June 15. The file is sent at hour 19. The reconciliation finds three problems. Receipts at the second site recorded the supplier’s code in a notes field, so 41 rows had to be keyed from scanned bills of lading. Twelve customer ship-tos had no phone number. And the WMS export wrote TLC 00417B as 417B for one supplier. The defects become requirements: a TLC field on the receipt screen at both sites, a mandatory phone number on new ship-to records with a cleanup of existing ones, and a text-typed TLC column in the export. The second drill, six weeks later, is sent at hour 9 with no hand-keyed rows.
The same drill doubles as user acceptance testing when you change systems. Add it to the test plan for any WMS, ERP or EDI change that touches receiving, production or shipping of listed foods.
What to do next
Start by finding out how far you are from one clean file today. Look first at data you already hold but cannot yet join.
- Confirm whether you are subject to the rule and whether the spreadsheet exemption in 1.1455(c)(3)(iii) applies, using the correct measure for your type of business.
- Flag every Food Traceability List item in the item master, with an effective date.
- List, for each KDE, the system and field where it lives today. The FSMA 204 KDE worksheet gives you the KDEs by event.
- Check that supplier TLCs and TLC sources are stored as data, not notes, at every receiving site.
- Build the location description view from site, supplier and customer masters, and fill missing phone numbers and addresses.
- Build and test the staging query that produces Receiving, Transformation and Shipping tabs for a given food and date range.
- Write the glossary and the runbook, and name the point of contact in your traceability plan.
- Run a timed mock request, then repeat it after fixing what it finds.
For how the capture and the export fit around an ERP and WMS you already run, see food traceability records. If the hard part is the joins between systems, that is the core of our ERP, WMS and TMS integration work. In our engagements we start by writing down where each field lives before building anything; if that would help, tell us about your setup.
