CUSTOM E-COMMERCE INTEGRATIONS · カスタム Eコマース連携

Japanese e-commerce integrations need to connect Shopify to Rakuten, Yahoo Shopping, and Amazon Japan — and the data sync between three distinct marketplace formats is the hardest part

Japan's e-commerce market does not operate on a single platform. Rakuten Ichiba, Yahoo Japan Shopping, and Amazon Japan each have distinct product data formats, inventory management requirements, and order management APIs. A DTC Shopify store selling across all three channels without automated data sync is managing four separate product catalogues and four inventory pools manually. The operational load is significant, and the error rate on manual inventory management across multiple channels grows with volume. Ignited Nepal builds the integration architecture that connects Shopify as the master catalogue and inventory source to Rakuten, Yahoo Japan Shopping, and Amazon Japan — with automated product feed submission, real-time inventory sync, and order routing back to Shopify for unified fulfilment management.

Request an Integrations Brief → View the evidence →
This is for you if

Who This Is For

Japanese DTC Shopify brands selling across multiple marketplace channels, using domestic carriers for fulfilment, or accepting konbini payment — where manual data management across platforms is the current bottleneck.

What's broken

The Problems We Fix

No inventory sync between Shopify and Rakuten Ichiba

Brands selling the same SKUs on Shopify and Rakuten Ichiba without an inventory sync are managing two stock pools manually. When a SKU sells on Shopify, the Rakuten listing still shows the pre-sale stock figure until someone manually updates it. The same SKU selling simultaneously on both channels without a sync causes overselling. Rakuten's RMS API (Rakuten Merchant Server API) allows inventory updates programmatically. An integration layer that listens for Shopify inventory change events and pushes the updated stock figure to Rakuten via RMS API keeps both channels in sync from a single inventory source.

Yahoo Japan Shopping product feed not automated from Shopify

Yahoo Japan Shopping requires product data submitted in a specific CSV or API format that differs from Google Shopping's feed structure. Shopify does not include a native Yahoo Japan Shopping feed connector. Product titles, descriptions, prices, and images need to be reformatted and submitted to Yahoo Shopping's Merchant API on a scheduled basis or triggered by product updates in Shopify. A custom feed connector reads Shopify product data via the Admin API, transforms it to Yahoo Japan's required format, and submits it to the Yahoo Shopping Merchant API.

Yamato Transport or Sagawa label not automated from Shopify

Yamato Transport (ヤマト運輸) and Sagawa Express (佐川急便) are Japan's two dominant domestic parcel carriers. Neither integrates natively with Shopify's shipping label workflow. Japanese fulfilment teams booking Yamato or Sagawa shipments manually via the B2 Cloud (Yamato) or e-飛伝 (Sagawa) carrier portals are performing a manual step that the carrier APIs can automate. Yamato's B2 API and Sagawa's e-飛伝Web API both accept shipment booking requests and return tracking numbers, which are written back to the Shopify order via the Fulfilment API.

Konbini payment reconciliation not automated

Shopify stores accepting konbini (convenience store) payment via GMO Epsilon, SBPayment, or Komoju receive a payment confirmation from the payment provider when the buyer pays at the konbini. This confirmation event does not automatically update the Shopify order status from pending to paid in most implementations. The result is a queue of pending Shopify orders awaiting manual review to determine which have been paid at the konbini and which have not. An automated webhook listener from the payment provider updates the Shopify order status and triggers fulfilment on confirmed konbini payment events.

What we engineer

What We Build

Shopify to Rakuten Ichiba inventory sync

Shopify to Rakuten Ichiba inventory sync via RMS API, triggered by Shopify inventory change webhooks and updating Rakuten stock figures in real time

Yahoo Japan Shopping product feed connector

Yahoo Japan Shopping product feed connector reading Shopify product data and submitting formatted product data to Yahoo Shopping Merchant API on schedule or on product update

Yamato B2 API or Sagawa e-飛伝 Web API integration

Yamato B2 API or Sagawa e-飛伝 Web API integration with Shopify, generating domestic shipping labels automatically at dispatch and writing tracking numbers back to Shopify orders

Konbini payment confirmation webhook listener

Konbini payment confirmation webhook listener updating Shopify order payment status and triggering fulfilment on confirmed payment events from GMO Epsilon, SBPayment, or Komoju

Unified order management view in Shopify

Unified order management view in Shopify that aggregates orders from Shopify DTC, Rakuten, and Yahoo Japan Shopping channels

Request an Integrations Brief →
What changes

What Changes After These Integrations Are Built

Before
After
Before Third-party Shopify payment apps for Nepali gateways are published by developers who do not always maintain them through eSewa or Khalti API updates. When the gateway provider updates their authentication flow or endpoint structure, the app breaks. Buyers who tap "Pay with eSewa" and hit a redirect error abandon the cart. The store owner files a support ticket with the app developer and waits. A custom-built Shopify Payment Provider extension built directly against the official eSewa Payment API or Khalti Payment API does not have this dependency. The integration is maintained by the team that built it. When the gateway updates, the extension is updated.
After Checkout completion rate improves. When eSewa and Khalti work reliably on the first tap, buyers complete their purchase. The abandoned carts caused by redirect errors stop appearing in your analytics.
Before After each order, someone on the fulfilment team opens the courier portal, enters the recipient name, address, phone number, item weight, and value, books the shipment, and copies the tracking number back into Shopify. For stores processing 20 or more orders per day, this is a meaningful portion of a working day. Pathao Courier and Karnali Express both have API capability for order creation and tracking updates. Shopify can trigger a courier API call the moment an order is marked ready to ship. The tracking number returns to Shopify automatically and is sent to the buyer. The manual booking queue disappears.
After Fulfilment team time shifts to higher-value work. Manual courier booking is gone. The team member who spent 90 minutes per day entering shipment details into the courier portal now processes exceptions, handles customer queries, and manages returns.
Before Nepali export brands selling handmade goods, textiles, or craft products to gift shops and boutiques in Australia, the US, and the UK typically manage wholesale orders outside Shopify entirely. Buyers email a product list request, the seller replies with a price sheet, the buyer responds with an order, and the seller manually enters it. There is no order history, no self-service reorder, and no automated invoice. A Shopify B2B portal gives wholesale buyers their own login, shows them wholesale pricing, enforces minimum order quantities, and supports NET 30 payment terms. Orders flow directly into Shopify. The seller's fulfilment team sees them alongside DTC orders and processes them in the same workflow.
After Wholesale revenue becomes measurable. When wholesale buyers order through a self-service portal instead of WhatsApp, every order is recorded in Shopify. You have wholesale order history, repeat order rates, and revenue per buyer for the first time.
Before Brands selling on both Shopify and Daraz Nepal maintain two product catalogues and two inventory counts. When a SKU sells out on Daraz, the Shopify inventory does not update. When the Shopify store runs a sale and changes pricing, Daraz still shows the old price. When the same item sells on both platforms within minutes of each other, the store oversells. A custom integration against the Daraz Seller API syncs inventory counts and product data from Shopify to Daraz in real time. The Shopify store becomes the single source of truth for product data, pricing, and stock levels across both channels.
After Daraz and Shopify stop contradicting each other. Your inventory count is accurate on both channels. Buyers on Daraz see the correct stock and the current price. Oversell incidents stop.
How it works

How We Build Custom Integrations

  1. 01

    Integration Audit

    Week 1

    We review your current Shopify setup, your active payment gateways, your fulfilment workflow, and any existing third-party apps you rely on. We document what is working, what is failing, and what is absent. We confirm the technical approach for each integration: which API endpoints are available, what authentication method each gateway or courier uses, and what data flows need to be built.

  2. 02

    Integration Specification

    Week 1-2

    We write a one-page specification per integration covering the data flow, the trigger points, the error handling approach, and the test criteria. You review and approve the specifications before any development begins.

  3. 03

    Development

    Weeks 2-5

    We build each integration in a Shopify development environment. For Payment Provider extensions, we build against the official gateway sandbox environment before any connection to live payment credentials. For courier integrations, we test order creation and tracking return flows before connecting to your live account.

  4. 04

    Testing and Handover

    Week 5-6

    We run end-to-end tests across each integration: payment flows from add-to-cart through to order confirmation, courier booking from Shopify order to tracking number return, and B2B order flow from buyer login through to Shopify admin order creation. We document each integration and provide your team with the operating instructions.

  5. 05

    Post-Launch Support

    We monitor each integration for the first 30 days post-launch. If a gateway or courier API update affects the integration, we update it. We offer a retained support arrangement for ongoing API maintenance.

Request an Integrations Brief →
Common questions

Frequently Asked Questions

How do I sync Shopify inventory with Rakuten Ichiba in real time?

Shopify fires an inventory_levels/update webhook each time inventory changes at a location. A middleware service subscribed to this webhook reads the updated inventory figure and calls Rakuten's RMS API (specifically the updateItem or inventory management endpoint) to set the equivalent Rakuten item stock to the same figure. The middleware must map Shopify variant SKUs to Rakuten item management numbers (管理番号). Discrepancies between Shopify and Rakuten SKU structures are the most common implementation challenge and require a mapping table maintained in the integration layer.

How do I automate Shopify product data submission to Yahoo Japan Shopping?

Yahoo Japan Shopping's Merchant API accepts product data in a defined CSV schema or via direct API calls. A scheduled job (daily or triggered by Shopify product update webhooks) reads Shopify product data via the Admin API (titles, descriptions, prices, images, variants), transforms it to Yahoo Japan's required field mapping, and submits it to the Yahoo Shopping API. Product data transformation is the most labour-intensive part — Yahoo Japan's category taxonomy and required attribute fields differ substantially from Shopify's product schema, and the mapping must be configured per product category.

How do I integrate Yamato Transport or Sagawa shipping labels with Shopify in Japan?

Yamato's B2 Cloud API and Sagawa's e-飛伝 Web API both accept shipment booking requests containing recipient address, package dimensions, weight, and service type, and return a tracking number and printable label data. The integration triggers on the Shopify orders/fulfilled webhook (or a Shopify Flow action), passes order delivery address and package data to the carrier API, receives the tracking number, and calls Shopify's Fulfilment API to record the tracking number on the order. The physical label is generated at the carrier system level and printed at the warehouse.

How do I automate konbini payment confirmation and Shopify order status update?

GMO Epsilon, SBPayment, and Komoju all send webhook notifications when a konbini payment is confirmed. A webhook endpoint in the integration layer receives the payment confirmation event (which includes the order reference number and payment amount), verifies the payment amount matches the pending Shopify order, and calls Shopify's POST /admin/api/orders/{order_id}/transactions.json endpoint to record the payment and update the order status to paid. Shopify then triggers the fulfilment workflow for that order automatically.

What is the best middleware for connecting Shopify to multiple Japanese marketplace channels simultaneously?

There is no single off-the-shelf middleware that handles Shopify, Rakuten, Yahoo Japan Shopping, and Amazon Japan in one integration with full API coverage for the Japanese market. The practical options are: an iPaaS platform (Make, Celigo, or Boomi) configured with custom API connectors for each Japanese marketplace; a Japan-specific multi-channel middleware such as Hamee's Nexway or Hunterz; or a custom-built integration layer specific to the brand's SKU structure and channel requirements. The right choice depends on the complexity of the product catalogue, the volume of orders, and the degree of customisation required per channel.

Start here

Request an Integrations Brief

If your eSewa or Khalti checkout is unreliable, your courier dispatch is manual, or your wholesale buyers are still ordering via WhatsApp, the problem is a missing integration, not a missing app. We will review your Shopify setup, identify the specific integration gaps, and give you a plain-language brief covering what needs to be built, how long it will take, and what it will cost.

Request an Integrations Brief →