01
Use the current template
Download the template available in your order-entry workspace and read the columns it actually expects. Keep one order per row and place each value in its own column. Do not assume a generic internet template matches the platform’s product selection or quantity fields.
Keep phone numbers as text so spreadsheet formatting does not remove a leading zero. A phone written in scientific notation is not a usable customer contact.
02
Verify the customer and product
Check the customer’s name, phone, city, clear address and agreement to order. Match the item to the intended active catalog product rather than choosing an approximate name. Confirm quantity and current availability before attempting submission.
Do not invent missing addresses or use demo contacts in a real import. If the product cannot be mapped confidently, resolve the row before sending it.
03
Review duplicates before import
Look for repeated rows and for customers whose request may already have been entered manually. A repeated phone does not always prove a duplicate, but the product, quantity and order context need review. Do not treat repeated rows as additional demand automatically.
Use the import preview and column mapping to inspect the parsed values. Fix rejected or ambiguous rows instead of approving the entire file without reading the result.
04
Read each submission result
After submission, review the per-row outcome and confirm the successful orders in your order list. A selected file is not proof that every row was saved. Keep failed rows separate so you do not blindly resubmit rows that already succeeded.
Protect the spreadsheet because it contains personal customer details. Share only through authorized channels and never publish it as a campaign example.