Introduction
A stock workbook has separate tabs for drinks, snacks and loading instructions. Procurement saves it as a CSV and sends one file to the vending supplier. The supplier successfully opens that file, but only the currently active stock sheet is present. The handoff looks successful while its intended scope remains incomplete.
Microsoft’s official text-format guidance lists several CSV formats as saving only the active sheet. It also warns that saving a workbook in any text format removes all formatting, and that some data and features may not be saved when changing format. A workbook and its export therefore need separate acceptance evidence.
This guide addresses coverage and operational meaning across that boundary. It does not claim that any particular machine imports CSV, preserves workbook features or interprets colours. Encoding, date interpretation and product identifiers need their own checks. Here the buying question is simpler: did the agreed handoff include everything it was supposed to include?
Quick Answer
Before exporting, create a short scope record listing each worksheet, its purpose and its intended destination or explicit exclusion. Confirm the actual file format supported by the receiver. Export through an agreed route, preserve the source workbook and inspect the files themselves before approving the handoff.
Do not rely on tab count, workbook name or a successful file-open message. For the CSV comma-delimited, Macintosh and MS-DOS formats listed by Microsoft, only the active sheet is saved. If the project needs several sheets, agree separate files or a controlled consolidation procedure and account for each source in the result.
Replace colour-only meaning with explicit owner-approved data or accepted instructions. Since text exports remove formatting, a red fill that means “do not load” cannot be treated as a transmitted control. Decide how that meaning will reach the operator or receiver and demonstrate the agreed result.
Source reviewed 11 October 2026: Microsoft Support — Save a workbook to text format (.txt or .csv). The examples below are proposed handoff checks, not a completed workbook export or independent equipment test.
Comparison Table
| Handoff approach |
Evidence to request |
Boundary to resolve |
| Workbook retained as source |
Version, sheet inventory and approved ownership |
Does the receiver actually accept this workbook type? |
| One listed CSV export |
Identity of the active source sheet and inspected output |
Other tabs are not established as included |
| Separate files for several sheets |
One coverage entry per exported source and destination |
Headers and row meanings may differ between files |
| Approved consolidated table |
Documented mapping from each included source |
Combining sheets must preserve their intended distinctions |
| Instruction information |
Explicit accepted fields or separate instruction record |
Text export removes the workbook’s visual formatting |
The right approach depends on the receiver and the owner’s record model. A single file can be sufficient for a single agreed sheet. A multi-file package can be appropriate for distinct tables. A consolidated table needs a mapping, rather than an assumption that all tabs can simply be stacked together.
Who Should Buy This
Use this brief when an equipment quotation includes stock-data handoff and procurement receives a workbook with more than one relevant tab. It also suits distributors preparing separate product categories, operators maintaining loading instructions in coloured sheets and buyers who need evidence that a launch package covers its intended stock.
Involve the workbook owner and the receiving supplier. The owner identifies what each tab means and whether it belongs in the handoff. The supplier declares the accepted file structure and destination. A reviewer then checks the actual outputs against those declarations. This avoids making the installer infer scope from a filename.
An external-only stock process still benefits from coverage acceptance. If the cabinet never imports the file, specify that the export goes to an operator or another system. The equipment brief should accurately identify who receives the data and what they do with it.
How We Evaluate Smart Vending Machines
The equipment below is shortlisted using public WEIMI product listings. We have not tested workbook exports, machine importers or stock controls. Public features help identify a physical format for quotation; the data route needs its own written scope and demonstration.
Prepare a harmless demonstration workbook with two distinct stock tables and a separate instruction sheet. Give each table a small approved set of records and make the expected exported package explicit. Mark the example as a sample so that nobody treats the demonstration instructions as live stock decisions.
Ask the supplier or reviewer to identify the active sheet, the chosen format and each produced file. Inspect headers and expected records in the output. Compare them with the scope record. If a sheet is intentionally excluded, record why and how its required information will reach the responsible person instead.
Include an instruction represented visually in the source, then require its owner-approved meaning in the agreed destination form. The demonstration should show how meaning survives the removal of formatting. It should not pretend that a text file can carry a cell colour or that the receiving platform understands an invented instruction field.
Finally inspect the actual receiving result, if the quotation includes that route. Reconcile it with the exported package and preserve the source version used. An output-file check and a receiver check establish different boundaries; acceptance should account for both.
Key Buying Factors
A coverage manifest. Record each relevant sheet name, purpose, expected file or destination and inclusion decision. The manifest need not be complex. It must be clear enough that another reviewer can identify an omitted sheet without reconstructing the sender’s intentions.
Active-sheet evidence. Microsoft’s listed text and CSV variants commonly state that they save only the active sheet. Capture which sheet was active for each agreed export and inspect the produced data. Avoid generalising from one successful export to all possible file variants or application versions.
Explicit meaning. When a workbook uses fill colour, font styling or other formatting to communicate stock instructions, have the owner state that meaning in an agreed form. All formatting is removed in text formats according to the source. A reviewer must not invent a status merely because a cell appears coloured.
Schema agreement. A drinks table and a loading-instruction sheet can have different headers and row meanings. Agree whether the receiver expects separate files or a mapped consolidation. Combining unrelated tabs into one table can create a new interpretation problem even when no row is missing.
Version and naming control. Keep the original workbook and connect each output to its source version. A familiar filename does not prove the active sheet or contents are unchanged. Review the actual package delivered to the receiver, especially when repeated exports are made during commissioning.
Feature boundaries. Microsoft warns generally that some formatting, data and features might not be saved in another format. Identify which source features your project relies on and verify their intended destination individually. This guide does not claim a universal formula, chart or embedded-object preservation rule.
Best Smart Vending Machines
LISTING-BASED PROCUREMENT OPTION / 1
Single-Door AI Vision Smart Fridge for Packaged Drinks
The public listing describes camera-based packaged-goods checkout, five shelf levels with five baskets and a top screen or lightbox. Confirm the quoted cooling and physical configuration. This article treats the format as packaged-stock equipment, not a machine preparing fresh juice.
For a drinks-only source sheet, a single agreed file may cover the project. If the workbook also holds operator instructions, account for those separately. Ask the supplier which destination receives each part rather than assuming camera checkout accepts the entire workbook.
View public product listing
LISTING-BASED PROCUREMENT OPTION / 2
WM22 Snacks and Drinks Vending Machine
The WM22 page lists a 21.5-inch touchscreen, inventory management and cooling, with spiral, conveyor, direct-push and hanging delivery described as options. Confirm which mechanism the quotation supplies. General inventory management does not establish multi-sheet workbook support.
For snacks and drinks held on separate source tabs, require a scope decision for both. Ask whether the receiver uses separate files or an approved combined catalogue. The chosen dispensing mechanism still needs physical package acceptance, independent of whether the data package is complete.
View public product listing
LISTING-BASED PROCUREMENT OPTION / 3
Two Cabinets, More Choice: Snack & Drink Vending Station
The two-cabinet page shows a main display and an additional spiral stock area. It is a possible format for a broader snack-and-drink selection. Do not infer shared software, independent cooling, a second display or export coverage from the cabinet arrangement.
For a larger assortment, request a package review that traces each intended category or stock-location sheet to its receiving record. More physical storage can increase the handoff scope, but the hardware does not decide which tabs the exporter includes. Confirm the actual data responsibilities in the quote.
View public product listing
Feature Comparison
| Format |
Public evidence used |
Export-scope requirement to discuss |
| Single-door AI vision fridge |
Camera checkout and shelf arrangement |
Account for the drinks sheet and any separate instructions |
| WM22 |
Touchscreen, inventory management and delivery options |
Agree snacks-and-drinks source coverage and receiver structure |
| Two-cabinet station |
Main display with additional spiral stock area |
Trace every included source to its agreed destination |
None of these features proves that the quoted solution accepts an Excel workbook, combines tabs or preserves formatting. The shortlist provides purchasing candidates. The supplier’s supported file contract and observed receiving result provide the evidence for data acceptance.
Cost & ROI Analysis
Estimate the time spent discovering missing sheets, preparing replacement files and repeating catalogue review. Keep this labour estimate separate from equipment price and from any speculative effect on sales. A coverage procedure is useful only if the scope record is accurate and reviewers use it.
| Hypothetical assumption |
Arithmetic |
Illustrative result |
| Current monthly export rework |
5 incidents × 90 minutes |
450 minutes, or 7.5 hours |
| Remaining rework with an accepted scope record |
2 incidents × 90 minutes |
180 minutes, or 3 hours |
| Assumed avoided labour |
4.5 hours × $30 |
$135 per month |
| One-time scope and sample acceptance |
Assumed cost |
$540 |
| Simple recovery of that effort |
$540 ÷ $135 |
4 months if the assumed reduction occurs |
The inputs are hypothetical, not WEIMI pricing, measured savings or a customer case. They exclude equipment, software, integration, taxes and the consequences of omitted operating instructions. They assume that the procedure actually reduces rework without increasing other workloads beyond the estimate.
Measure source-sheet omissions and review time before attributing savings. A file that opens successfully is not evidence of lower costs. A complete export package still needs a supported receiving route, and supplier corrections can remain necessary even when scope is clearly documented.
Best Choice by Scenario
One agreed product sheet: confirm that it is the active exported sheet, inspect the resulting records and preserve the source. The simple scope should still be stated rather than assumed.
Separate snack and drink tables: agree two files or a controlled consolidation, depending on the receiver’s supported structure. Require evidence from each source. Do not let the active tab decide the commercial scope by accident.
Instructions live on a coloured tab: request explicit approved meaning and a separate destination where necessary. A plain-text stock file cannot be assumed to transmit workbook formatting.
A supplier offers workbook ingestion: ask for a demonstration of the exact supported workbook type and included sheet scope. The listed CSV export behaviour does not establish that supplier’s importer, and an importer claim does not eliminate the need for coverage evidence.
Applications
An office vending buyer can use the manifest when facilities provides a workbook containing products and refill instructions. The project should identify which information reaches the supplier and which remains with the operator. Neither team should assume the other received every tab.
A distributor preparing several categories can attach source-to-output mapping to the launch package. Each accepted file should have a defined role and a traceable source. A successful receipt of one category should not close the review for the remaining categories.
An operator with external stock records can apply the same scope discipline to files sent to a reviewer. The article does not require an in-machine importer. It requires the actual handoff to preserve the information the agreed workflow depends on.
FAQ
Does saving a stock workbook as CSV export every tab?
Microsoft’s listed CSV comma-delimited, Macintosh and MS-DOS formats save only the active sheet. Confirm the actual export route and inspect its output; do not treat the workbook’s tab count as proof of file coverage.
Will the supplier receive our coloured stock instructions?
The source states that all formatting is removed in text formats. If colour communicates an operational instruction, provide that meaning through explicit agreed fields or a separate accepted instruction record.
Should we combine every worksheet into one file?
Only if that matches the receiver’s agreed schema and the owner’s record model. Different tabs may contain different kinds of information. Choose separate accepted files or an approved consolidation process rather than combining them without a mapping.
Does the same filename prove the new export is complete?
No. Record the source version, intended sheet scope and actual file contents. A filename is a label; inspect headers, records and expected scope before handing the file to the receiver.
Can a receiver’s successful import prove all workbook tabs arrived?
No. Success for one file establishes only the observed result for that route. Reconcile every intended sheet or explicit exclusion against the exported package and destination evidence.
Have the three machines been tested with a multi-tab export?
No. The shortlist uses public equipment descriptions. The export checks are proposed procurement exercises, and any receiver format or import behaviour needs a separate supplier demonstration.
Final Recommendation
Accept the exported package against an explicit sheet-scope record, not against the workbook’s name or a file-open success. Preserve the source, inspect every intended output and provide operational meaning in a form that survives text export.
Select a public WEIMI format around the actual products and stocking arrangement. Where a data route is included, have the supplier declare its supported representation and demonstrate the destination coverage. The buyer should be able to account for every intended tab and every instruction before commissioning.
CTA
Send WEIMI your product categories, proposed stock-data route and sheet coverage requirements. Ask which files or workbook types the quoted solution supports, where instructions will be held and how the receiving result will be demonstrated. Harmless sample tables and an agreed scope record are sufficient for the initial discussion.
Get My Custom Quote
