Java fresh business platform - combat orders Architecture
Fresh electricity supplier in order center is a hub electricity supplier backend system, in order in this part needs to read this data and information is performed a plurality of processing modules, and flows to the next link; and the order module for an electrical supplier system, the importance of self-evident.
At the same time, the order is the core of a company to survive and even profit, while electricity supplier system order system is a carrier support order processing, order system so the design is very important.
First, the order architecture
To understand the order system, information architecture of our first orders from understanding the system up ordering system, so as to establish the overall awareness of the order system;
Second, the order status
Definition: To meet the needs and improve the efficiency of the organizational division of labor, the system will process the entire business transaction split into several controllable aspects.
1. Order a forward state
Payment pending: the user submits the order, no payments have been waiting for the user to pay, due to the pending order will lock stock, it will be automatically disabled after a timeout settings.
To be shipped: merchant shipping after payment from the user waits.
Inbound: merchant shipping to and wait for the user delivery.
Completed: After confirming receipt, order transaction is completed.
Canceled: to cancel the order before payment. Unpaid overtime or the user will have to cancel the order of this order status.
Aftermarket: User refund payment before shipment or after delivery business user application back, a replacement.
2. Orders sale status
Pending: After the user submits the return application, pending review of the state, the state paid the user to be shipped, the order has not been pushed to a warehouse or in a warehouse intercept shipments successful, the system can direct approval. When the audit is not passed, go back to the normal process.
Return to be put in storage: Return application review after the adoption, waiting for the user returns storage.
To be refunded: After a successful return storage, waiting for a refund to the user.
Ment to be put in storage: a replacement application approved, waiting for the user replacement storage.
The replacement library: After a replacement storage, generation replacement Delivery, order a library.
Aftermarket Success: After the return, refund success, success transfer to after-sales status, returns, refunds after-sales success belongs to the transaction to close in the main flow.
3. The flowchart of the single line
1. security verification process in order primarily to detect whether the user is on the blacklist, the user purchasing behavior and the like is normal, when the detected abnormal termination orders;
2. Get product information (SKU, size, price, etc.) from the center of commodities
3. Obtain from the center of commodity marketing, order promotions (coupons, promotions), judges whether preferential terms to calculate the discount amount.
4. Obtain Benefits of Membership in the Member Center, such as the integration platform deductible, coupon discount conditions.
5.在调度中心检验销售层库存，按照调度规则锁定区域库存。
6.根据拆单规则（商家，仓库，订单类型等）将订单拆分成若干个子订单，根据运费模板计算运费，根据商品金额，运费，优惠金额计算应付金额（实付款）。
三、优惠分摊
定义：是指在实际销售中将订单的优惠去分摊到每一件SKU中去结算。
订单实付金额=商品金额（SKU金额总计）+运费-总优惠金额
总优惠金额=促销活动优惠金额+优惠券优惠金额+虚拟币抵扣金额
按照商品比例分摊。
案例：
订单中有甲乙两店的商品A、B、C、D、E 包邮。商品A，D参加跨店满200减40的活动（活动1），商品B，C参加满100减10的活动（活动2）另外用户还使用了100元现金券。
订单优惠金额=40+10+100=150元.
依据优惠分摊原则：则各项的优惠金额为：
四、订单拆分
定义：为了方便订单的发货与结算，系统依据一定的规则（物流、仓库等因素）将用户订单拆分成若干个发货单。
不同店铺：在电商平台类架构下，由于商品归属权不同，涉及财务结算和物流发货的问题，需要根据店铺归属问题对订单进行拆单。例如淘宝，天猫的商品在下单时会将订单根据不同店铺进行拆分成若干个子订单。
不同仓库：若同一订单分散在不同仓库，则应按照仓库归属进行拆分订单。当一件商品在多个仓库有货时，应根据物流的区域的时效选择仓库进行拆单。
不同品类：由于商品的属性不同一样会产生拆单需求，例如易碎品需要特殊包装，超大物品（钢琴，座椅）需要单独包装。有些商品不能放在一起，同样需要拆单。
物流因素：不同物流公司对单个包裹的重量或体积都有特殊要求，需要根据SKU的毛重和体积来计算包裹的总重量和体积，超出物流公司限制的也需要拆单。
商品价值：根据商品价值需要拆单的主要涉及海淘和跨境的商品；国家对每笔跨境订单有单次限额，对年度跨境商品订单总金额也有限制，当单次购买金额超过限制金额时，也需要对订单进行拆单。
