How to Import Dates into Shopify and Handle Order Date Formats and Limits

Shopify import dates work differently depending on what you’re importing. You can set dates in date-type metafields, and order import tools can keep each order’s original date, but Shopify always records the moment a record was created in its own database. Product and customer CSV files have no column for setting a creation date at all.

Knowing which dates you control, and which format Shopify expects, prevents two common problems: dates that Excel quietly reformats, and imported orders that show today’s date instead of when they were actually placed.

Which Dates You Can Set When Importing to Shopify

Most of the dates you see in Shopify are set automatically and can’t be changed by an import. The table below shows what you can control for each type of data:

For products and customers, this means imported records look new in Shopify, even if they existed for years on another platform. If you need to keep an original date for reference, such as when a product was first launched, store it in a date metafield instead.

Orders are the exception, because order import tools can set a processed date that reflects when the order was really placed. That date is what keeps your sales history accurate, as covered in the section on order dates below.

Use the Right Date Format

Shopify expects dates in ISO 8601 format, which runs from the largest unit to the smallest. A date-only value looks like 2026-10-10, while a date and time looks like 2026-10-10T14:30:00Z. For date-and-time metafields, Shopify stores the time in UTC.

The Z at the end of a date-and-time value means UTC, so convert local times before importing. For example, 10:30 AM Eastern Daylight Time is four hours behind UTC, so it becomes 2026-10-10T14:30:00Z. Skipping that conversion shifts every time by your offset from UTC, which can move late-evening events onto the next day.

Stop Excel from reformatting dates

Excel is the most common reason correctly typed dates fail. When you type or open 2026-10-10, Excel recognizes it as a date and may save it in your computer’s regional format, such as 10/10/2026. The file then reaches Shopify in a format it doesn’t accept.

To prevent this, format date columns as Text before entering or pasting values. If you’re opening an existing CSV, use Data > From Text/CSV and set date columns to Text during import, rather than double-clicking the file. After saving as CSV UTF-8, open the file in a plain text editor to confirm the dates still read 2026-10-10.

Google Sheets can do the same thing, so check its output too. The safest test is to import one or two rows, then open the record in Shopify and confirm the date shows as expected.

Keep Original Order Dates When Importing Orders

Shopify’s admin has no built-in order import, so orders come in through an app or the API. These tools set the order’s processed date from your file, which is the date Shopify uses to represent when the order was placed. If the date isn’t mapped, Shopify uses the import date instead, and every historical order appears as if it happened today.

Before importing, map your source file’s order date to the processed date field in your tool. Map transaction dates too, if your tool supports them, so payment records match the original orders. Use the ISO 8601 format and convert times to UTC, as described above.

Why exported order dates can look wrong

Even with correct processed dates, Shopify’s own order export can show the import date. The export’s Created at and Paid at columns come from the order’s internal created date, which Shopify sets when the record is added and which no app can change. The processed dates you imported aren’t included in that export.

This is a display issue in the export, not a sign your import failed. To get the original dates into a spreadsheet, use an export app that can include the processed date fields. Shopify’s own order pages and the processed date are what reflect when each order was placed.

Check reports and avoid duplicate date ranges

Imported orders become part of your store’s data, so they can change your analytics. Check how your tool’s processed and transaction dates appear in reports by running a small real import first. Test orders aren’t a substitute here, because Shopify keeps them out of reports and analytics.

Be careful when importing orders in date-range batches. Some tools detect duplicates only by order number, so overlapping date ranges need care to avoid importing the same orders twice. Keep a record of which ranges you’ve imported, and make each batch start where the previous one ended.

Some order dates live outside the standard fields. For example, ship-by or delivery dates from apps and channels are often stored as order note attributes with names such as “Delivery Date,” usually in UTC ISO 8601 format. If another system reads those dates, follow its required field name and format exactly.

Schedule Imports for a Specific Date

Sometimes the date that matters is when the import runs. Shopify’s built-in CSV import starts immediately, but some import tools let you schedule an import for a specific date and time, or repeat it at set intervals. This is useful for changes that should take effect at a planned moment, such as a price update for a sale or a recurring stock update from a supplier file.

Bulkflow supports scheduled data updates along with bulk import and field mapping for Shopify, which suits updates that need to happen on a set schedule. Whichever tool you use, check which time zone its schedule uses, and test the import file on a few products before the scheduled run.

Conclusion

Getting Shopify import dates right comes down to knowing which dates you can set, writing them in ISO 8601 format and protecting them from spreadsheet reformatting. With processed dates mapped for orders and dates stored in metafields where you need them, your imported data keeps its real history. We hope this guide helps you handle dates confidently in your next Shopify import. If scheduled and recurring imports are part of your workflow, you can explore Bulkflow.