Retrieve Order Number (注文番号), Total (合計金額), and Estimated Delivery (お届け予定日) from a Rakuten Order Screenshot
Manually copying order data from a Rakuten Ichiba screenshot takes 3 minutes per order — this retrieves the order number, product title, total, and estimated delivery date in 5-10 seconds, no Japanese reading required.
5-10s per screenshot · Up to 99% accuracy on printed text
Every Rakuten Order Confirmation Has These Four Fields
All labeled in Japanese (日本語) and split across per-store layouts. With Custom Column Extraction, type fields in English and the AI reads each Japanese label for the value.
A 10-12 digit numeric string — the master key across 50,000+ stores. Each store assigns its own internal reference, but the 注文番号 is the only universal identifier on the platform.
Japanese name with optional model code. Mobile screenshots truncate after 30-40 characters — the AI extracts whatever is visible on the confirmation page.
The bottom-line figure — item price (商品代金) + shipping (送料) + tax (消費税) − Super Points redeemed (ポイント利用). Define a "Total" column and the AI reads the label to find the right number.
Each store sets its own shipping terms, carrier, and processing time — the お届け予定日 reflects that store's logistics setup. Some ship via Sagawa Express, others via Japan Post or Yamato Transport, with delivery windows to match.
50,000+ Stores, 50,000+ Layouts — Same Four Fields
Rakuten Ichiba is not one store — it is 50,000+ independent sellers, each with their own order confirmation layout, shipping terms, and formatting. Template-based tools assume every order page looks the same. On Rakuten, they do not.
Every store has its own layout
Rakuten does not enforce one order confirmation template. Store A puts the order number at top-right in bold, Store B nests it inside a compact shipping table, Store C renders it in a long receipt-style scroll. A template tool trained on A fails on B and C — and there are over 50,000 stores to account for.
The split pricing hides internal complexity
A Rakuten order total is never one number. The confirmation shows 商品代金 (item price), 送料 (shipping), 消費税 (consumption tax), and ポイント利用 (points redeemed) as separate lines, then the final 合計金額. Standard OCR dumps these in reading order — you get a column of yen values with no way to tell them apart.
Per-store delivery estimates
Unlike Amazon's centralized logistics, each Rakuten seller ships independently — one via Yamato in 24 hours, another via Japan Post in 5 days. The Estimated Delivery (お届け予定日) label is always in Japanese but its format and position vary. A Reddit user noted "the Rakuten Ichiba webpage is a mess" — the order confirmation is part of that uneven experience.
Type English columns, AI reads Japanese labels
Define "Order Number (注文番号)", "Product Title (商品名)", "Total (合計金額)", "Estimated Delivery (お届け予定日)". The AI reads the semantic role of each label — it understands that 注文番号 means the order identifier regardless of where on the screen it sits. Same fields, every store, no layout training needed.
Split pricing becomes independent columns
Add separate columns for each component — Item Price (商品代金), Shipping (送料), Tax (消費税), Points Used (ポイント利用), Final Total (合計金額). The AI reads the label next to each value and maps it to the correct column, so a ¥4,800 item price and ¥350 shipping land in separate cells without manual sorting.
Cross-platform batches, one column set
The same four column definitions work for Rakuten, Amazon, Coupang, and any other platform in the same batch. The AI reads per-image — a Rakuten 注文番号 and an Amazon "Order #" land in the same "Order Number" column. One spreadsheet, multiple platforms, no manual merging.
From a Rakuten Order Screenshot to One Spreadsheet Row in Three Steps
Drop your Rakuten order screenshot — mobile app or desktop browser, any store, any carrier. JPG, PNG, or WebP from your camera roll or screenshot folder. If a multi-item order from a single store scrolls beyond one screen, take separate screenshots per visible section.
Type the four column names — Order Number (注文番号), Product Title (商品名), Total (合計金額), Estimated Delivery (お届け予定日). The AI reads every Japanese label and maps each value to the column you defined. Store A's layout, Store B's layout, Store C's layout — all processed with the same four column names.
Download a single Excel file with one row per screenshot — the order number, product title, total in yen, and per-store delivery estimate all in your columns. If you batch-process a month of Rakuten orders from ten different stores, every order lands as one row in the same spreadsheet (~3 min manual entry per screenshot vs ~5-10s here).
Where Rakuten Order Screenshot Extraction Works Best — and When to Double-Check
- ✓ Standard order confirmation screenshots from any Rakuten Ichiba store — the AI reads Japanese labels (注文番号, 合計金額, お届け予定日) and maps them to English column names by understanding what each field means, regardless of per-store layout differences.
- ✓ Split pricing breakdowns — define separate columns for item price, shipping, tax, and points deducted, and each component maps independently by its label.
- ✓ Cross-platform batches — Rakuten screenshots alongside Amazon, Coupang, or Shopee orders using the same four column definitions, all merged into one spreadsheet.
- ⚠ Rakuten Super Point earnings (獲得予定ポイント) shown as separate text — include a dedicated "Points Earned (獲得ポイント)" column if you need to capture point rewards independently from the total.
- ⚠ Heavily compressed screenshots re-shared through messaging apps — the AI still extracts the text, but fine details like small Japanese date text on the delivery estimate may degrade with compression.
- ⚠ Order confirmations that display the tracking number (配送伝票番号) only as a clickable link rather than visible text — capture the store's shipment notification separately if you need the tracking number itself.
Frequently Asked Questions
What is the Order Number (注文番号) on a Rakuten screenshot, and how is it different from the store's own reference number?
The Order Number (注文番号) is a 10-12 digit numeric string assigned by Rakuten's central system when you place your order. It is the only identifier that works across all Rakuten services — customer support, returns, point tracking. Some stores also display their own internal order reference (受注番号 or 注文ID) next to or below the 注文番号. The AI extracts them as separate fields if you define two columns — just include both "Order Number (注文番号)" and "Store Reference (受注番号)" in your column list.
Can I extract the Total (合計金額) as a single number, even though the Rakuten confirmation splits it across item price, shipping, tax, and point deductions?
Yes. The 合計金額 or ご請求金額 at the bottom of the Rakuten price breakdown is the sum of item price + shipping + tax minus any Super Points redeemed. Define a single "Total (合計金額)" column and the AI reads the label to locate the final number. If you also want the individual components, add separate columns for "Item Price (商品代金)", "Shipping (送料)", "Tax (消費税)", and "Points Used (ポイント利用)" — the AI maps each by its label and fills all columns in one pass.
Why does the Estimated Delivery (お届け予定日) change depending on which Rakuten store I order from?
Because each store in Rakuten Ichiba is an independent seller that manages its own shipping. Unlike Amazon where fulfillment is centralized, a Rakuten store in Osaka using Sagawa Express may deliver in 2-3 days while a store in Hokkaido using Japan Post may need 5-7 days. The お届け予定日 printed on the order confirmation reflects that specific store's processing time and its chosen carrier's service area. The AI extracts this date by reading the label — it does not need to know which store or which carrier.
Can I retrieve Rakuten order data using English column names even though the entire interface is in Japanese?
Yes — type your column names in English (Order Number, Product Title, Total, Estimated Delivery). The AI reads the Japanese labels (注文番号, 商品名, 合計金額, お届け予定日) by their semantic role — it understands that 注文番号 is the order identifier regardless of language. You do not need to know or type any Japanese characters. The output spreadsheet uses your English column headers with the extracted values.
Can I batch-process Rakuten screenshots alongside other ecommerce platforms like Amazon, AliExpress, or Coupang?
Yes — define your four column names once, upload a mix of Rakuten, Amazon, AliExpress, and Coupang screenshots into a single batch. The AI processes each image independently, reading the local-language labels (Japanese for Rakuten, English for Amazon, Chinese for AliExpress, Korean for Coupang) and mapping them to the same English column headers. The output is one spreadsheet with one row per screenshot — orders from four markets in a single table.
Back to the ecommerce order screenshots overview — see which other online order platforms this tool supports.
Read the full Rakuten order screenshot guide — a deep dive into order numbers, Rakuten Super Points, and delivery method identification.
Compare with Coupang — another Asian e-commerce giant with a loyalty-point system and localized delivery tracking, but in a single-market Korean interface rather than a decentralized store model.