The Excel export passes through an export guard before it writes the file: it's logged (who, when, how many rows), and for larger exports (40+ rows) the row order is subtly re-shuffled (a handful of adjacent rows swapped) so a leaked copy can be traced back to the export event. If your account crosses a daily row cap — a limit that is off by default and only applies if your kitchen's operator has explicitly configured one — the export is blocked outright with that message and an alert is sent to the platform operator. This is a data-leak-prevention control, not a bug — contact [email protected] if you legitimately need the limit raised.

Note: this guard currently applies only to the Excel export button. The Print/PDF view does not pass through it — printing or saving a PDF is never logged, watermarked, or capped this way.