DEV Community: Taocarts

Purchasing Transshipment + International Consolidation , Core Fulfillment Module Development for Reverse Overseas Purchasing

Taocarts — Thu, 28 May 2026 01:45:30 +0000

Developers familiar with the reverse overseas purchasing business model know clearly that the core profit link of the purchasing industry lies in the back-endpurchasing transshipment, purchasing consolidation and international warehousing fulfillment services, rather than simple product purchasing sales. 90% of open-source purchasing system source codes and purchasing mall systems on the market only realize front-end order placement and product procurement functions, completely lacking core fulfillment modules such as consolidation and parcel merging, logistics track tracking, overseas warehouse management and intelligent freight estimation, making them unable to support enterprise-level purchasing business deployment. Based on the practical development experience of Taocarts cross-border independent station system, this article deeply disassembles the technical implementation of the entire fulfillment system including consolidation and transshipment, overseas warehouse management, freight calculation and parcel pre-warning, and reviews the development difficulties and solutions of cross-border purchasing fulfillment modules.
For cross-border purchasing and reverse purchasing businesses, the fulfillment chain directly determines user experience and merchant profits. Most overseas customers will purchase multiple products from Taobao and 1688 and require unified consolidation, combined packaging and international transshipment, which demands complete parcel management capabilities of the system. Taocarts purchasing consolidation system allows users to pre-warn domestic express parcels with one click independently. After users send multiple purchased products to the domestic transit warehouse, they can input express numbers independently, and the system automatically identifies parcels, completes warehouse entry registration and classified storage. Merchants can merge or split parcels and provide value-added inspection and photo taking services in the background with full digital management, completely replacing the inefficient manual registration and bookkeeping mode of traditional purchasing businesses.
Intelligent freight estimation is the core difficulty in logistics fulfillment development. Freight rates vary greatly according to parcel weight, volume, destination country, logistics channel and seasonal fuel surcharges. Ordinary overseas purchasing systems adopt fixed freight templates, easily leading to customer loss due to over-quotation or merchant losses due to under-quotation. Taocarts is built with an intelligent freight estimation algorithm that automatically calculates accurate freight based on parcel weight, volume, destination country, logistics channel and real-time fuel rates. Matched with the automatic tariff calculation function, it informs customers of the total cost in advance and eliminates after-sales disputes fundamentally.
Overseas warehouse management is a rigid demand for medium and large cross-border purchasing enterprises and a major shortcoming of most source code systems. Taocarts overseas warehouse purchasing system realizes full-process digital management of inventory storage, warehouse entry, shelf placement, outbound delivery and inventory early warning. It supports multi-warehouse zoning management and batch management, especially suitable for refined management of high-value goods such as sneakers, streetwear and luxury goods. It supports LJR, BV and other sneaker batch classification and archiving to solve the problem of confused inventory management in trendy product purchasing.
The following shares the practical core code of freight estimation and parcel consolidation calculation developed based on Laravel, adapting to all international consolidation scenarios:

<?php
namespace App\Services\Logistics;

// Cross-border consolidation intelligent freight calculation service
class FreightCalculateService
{
    // Basic freight rate configuration by weight range
    protected $weightRate = [
        0 => 18,  // 0-1kg first weight unit price
        1 => 12,  // 1-5kg additional weight unit price
        5 => 10,  // Unit price for weight over 5kg
    ];

    // Calculate total consolidation freight
    public function calculateTotalFreight(float $weight, string $country, float $volume = 0): array
    {
        // Basic freight calculation
        $basePrice = $this->getBaseFreight($weight);
        // Fuel surcharge
        $fuelPrice = $this->getFuelSurcharge($weight);
        // Remote area surcharge by country
        $remotePrice = $this->getRemoteSurcharge($country);
        // Volume weight correction
        $volumePrice = $volume > 0 ? $this->getVolumeFreight($volume) : 0;

        $total = $basePrice + $fuelPrice + $remotePrice + $volumePrice;
        return [
            'base_price' => $basePrice,
            'fuel_price' => $fuelPrice,
            'remote_price' => $remotePrice,
            'total_price' => round($total,2)
        ];
    }

    // Calculate basic weight freight
    protected function getBaseFreight($weight)
    {
        if($weight <= 1) return $this->weightRate[0];
        elseif($weight <=5) return $this->weightRate[0] + ($weight-1)*$this->weightRate[1];
        else return $this->weightRate[0] + 4*$this->weightRate[1] + ($weight-5)*$this->weightRate[2];
    }

    // Dynamic fuel surcharge calculation
    protected function getFuelSurcharge($weight)
    {
        $baseFuel = 3;
        return $baseFuel + round($weight * 0.5,2);
    }

    // Remote area additional fee verification
    protected function getRemoteSurcharge($country)
    {
        $remoteList = ['US','CA','AU'];
        return in_array($country, $remoteList) ? 8 : 0;
    }
}
?>

Front-end parcel pre-warning and logistics track query interface encapsulation:

// Purchasing consolidation parcel pre-warning API
import request from '@/utils/request'
export const addPackageForecast = (data) => {
  return request({
    url:'/api/logistics/package/forecast',
    method:'post',
    data:{
      express_no: data.expressNo,
      source_warehouse: data.warehouse,
      remark: data.remark || 'Regular purchasing parcel'
    }
  })
}

// Real-time logistics track query
export const getLogisticsTrack = (packageId) => {
  return request({
    url:'/api/logistics/track',
    method:'get',
    params:{ package_id: packageId }
  })
}

In actual development and deployment, we have optimized the value-added inspection service module and developed customized photo templates. The system supports automatic in-warehouse shooting, multi-angle retention and defect marking, solving the high return rate pain point caused by overseas customers’ inability to view physical products. This refined function is rarely covered by ordinary purchasing website development projects. Meanwhile, the DIY shopping function is added to support users in independently matching multi-platform products and freely combining consolidated parcels, greatly improving personalized shopping experience.
From a technical development perspective, the fulfillment module of reverse overseas purchasing and cross-border purchasing systems is the core standard to distinguish amateur source codes from commercial systems. Without complete consolidation and transshipment, overseas warehouse management, freight accounting and logistics tracking functions, gorgeous front-end pages cannot support long-term business operation. Through the self-developed full-link fulfillment module, Taocarts realizes a one-stop closed loop covering product purchasing, automatic procurement, consolidation and transshipment, overseas warehousing and international delivery, providing a complete technical solution for cross-border purchasing entrepreneurs.

Full-Stack Architecture Practice of Reverse Cross-Border Purchasing System: React + Vue + Laravel + Express Collaborative Development Review

Taocarts — Thu, 28 May 2026 01:25:10 +0000

With years of in-depth development experience in reverse purchasing and cross-border independent station tracks, I have found that most open-source purchasing system source code and generic purchasing mall projects suffer from loose architecture, serious front-end and back-end coupling, poor high-concurrency fault tolerance, and conflicting multi-business modules. Many individual developers and small technical teams make a common mistake when building a reverse overseas purchasing system — they blindly adopt universal e-commerce frameworks while ignoring exclusive business logic of cross-border purchasing, purchasing consolidation, and transshipment fulfillment. This eventually leads to frequent online bugs such as overselling, delayed data synchronization, and disordered orders. Combining the landing and iteration experience of the Taocarts cross-border independent station system, this article fully disassembles the full-stack technical architecture adapted to Taobao 1688 purchasing system and cross-border purchasing scenarios, shares practical optimization ideas for multi-framework collaborative development, and provides valuable references for peers engaged in cross-border e-commerce system development.
The complete cross-border purchasing system of Taocarts adopts a mature and stable hybrid technology stack. The front end integrates React and Vue.js, mobile terminals are developed based on React Native, and the back end adopts a dual-engine architecture of Laravel and Express.js, which is completely different from ordinary purchasing systems built with a single framework. The core reason for adopting multi-framework collaboration is to adapt to the diversified scenarios of cross-border independent stations. Vue.js is lightweight and fast in iteration, suitable for conventional front-end scenarios such as official website display, product browsing, member center, points and coupon management. React features a complete ecosystem and high componentization, perfectly adapting to high-frequency interactive scenarios including DIY shopping, multi-currency dynamic rendering, and complex order filtering. React Native ensures consistent cross-terminal experience for mobile apps and mini-programs. On the back end, Laravel undertakes core businesses including permission management, member system, order processing and data persistence, while Express.js is lightweight and efficient, specially handling high-concurrency lightweight requests such as API synchronization, logistics callbacks and third-party platform docking. The division of labor effectively solves the stuttering and slow response problems of traditional purchasing mall systems.
Developers with cross-border purchasing development experience are well aware that the core pain points of the reverse overseas purchasing business model lie in the compatibility and stability of multi-business modules, rather than simple page display. Most open-source purchasing source codes only realize basic product display and order placement functions, completely lacking core capabilities such as purchasing transshipment, international consolidation, overseas warehouse management and multi-platform supply synchronization, making them impossible for commercial deployment. In the architectural design stage, Taocarts has split five core business micro-modules: supply collection module, automatic purchasing module, consolidation and transshipment module, member marketing module, and multi-platform dropshipping module. These modules are low-coupling and high-cohesion, supporting independent iteration and customized development, which explains why the system can adapt to segmented tracks including overseas Chinese purchasing, sneaker and streetwear purchasing, luxury purchasing, and electronic product purchasing.
The following part shares the practical code of core architecture initialization and cross-framework interface joint debugging, solving common cross-domain and data format inconsistency problems between Vue/React front end and Laravel back end.

// Express.js cross-domain and unified API encapsulation (for Taobao/1688 supply synchronization)
const express = require('express');
const cors = require('cors');
const app = express();

// Adapt multi-terminal cross-domain, compatible with multi-domain deployment of cross-border independent stations
app.use(cors({
  origin: [
    'https://www.taocarts.com',
    'https://m.taocarts.com',
    'http://localhost:8080'
  ],
  credentials: true,
  maxAge: 86400
}));

// Unified global response format to avoid front-end and back-end parsing exceptions
app.use((req, res, next) => {
  res.success = (data, msg = "Operation Success") => {
    res.json({ code: 200, data, msg, timestamp: Date.now() })
  }
  res.error = (msg = "Operation Failed", code = 500) => {
    res.json({ code, data: null, msg, timestamp: Date.now() })
  }
  next()
})

// Unified registration of supply API synchronization routes
app.use('/api/source', require('./routes/source'));
module.exports = app;

Core Laravel permission middleware code to ensure data security of purchasing orders, supply data and overseas warehouse information:

<?php
namespace App\Http\Middleware;

use Closure;
use Illuminate\Http\Request;

// Exclusive permission verification middleware for cross-border purchasing system
class CrossBorderAuth
{
    public function handle(Request $request, Closure $next)
    {
        $token = $request->header('Authorization');
        // Isolate background management and front-end user permissions
        if(!$token && !in_array($request->path(), ['api/goods/list','api/rate/query'])){
            return response()->json(['code'=>401,'msg'=>'Permission denied, please log in']);
        }
        return $next($request);
    }
}
?>

In actual development and iteration, the biggest pitfall I have encountered is adapting full business scenarios with a single framework. The early test version adopted full Vue development, resulting in redundant components and page stuttering when processing complex logic of the purchasing consolidation system such as parcel merging, freight calculation and logistics track rendering. Later, we reconstructed high-frequency interactive modules with React and used Express to handle high-concurrency requests, increasing the system QPS by more than 60%. For developers building reverse overseas purchasing independent stations, do not blindly pursue technical unification. It is necessary to select technologies based on business scenarios: Vue for lightweight display scenarios, React for high-interaction and calculation-intensive scenarios, Express for high-concurrency interfaces, and Laravel for core business guarantee. This is the optimal technical solution for commercial-grade purchasing systems.
In addition, commercial purchasing systems must abandon the extensive development mode of open-source source codes. Most free purchasing system source codes on the market lack data fault tolerance and concurrency processing, causing duplicate orders and inventory disorder when order volume surges. The Taocarts architecture integrates request anti-shake, idempotency verification, regular data backup and interface circuit breaker mechanisms. Exclusive anti-shake logic is configured for multi-platform API synchronization of Taobao, 1688, Vipshop and other platforms to avoid platform interface current limiting caused by frequent requests, building the core technical barrier for stable enterprise-level cross-border purchasing business support.
Overall, the development of reverse overseas purchasing and cross-border purchasing systems is no longer a simple mall site building project, but a comprehensive system engineering integrating supply docking, automatic purchasing, international consolidation and transshipment, overseas warehouse management, multi-currency payment and private domain member operation. As technical developers, only by thoroughly understanding business logic and optimizing technical architecture in a targeted manner can we develop commercial-grade cross-border independent station systems that are deployable, profitable and iterable in the long run.