package common.ecommerce.hengjian.adapter; import com.fasterxml.jackson.databind.JsonNode; import common.ecommerce.hengjian.dto.HengjianAddressClassificationDtos; import common.ecommerce.hengjian.dto.HengjianCancelOrderDtos; import common.ecommerce.hengjian.dto.HengjianCarrierGroupDtos; import common.ecommerce.hengjian.dto.HengjianBoxLabelDtos; import common.ecommerce.hengjian.dto.HengjianCreateOrderDtos; import common.ecommerce.hengjian.dto.HengjianDestructionDtos; import common.ecommerce.hengjian.dto.HengjianFeeEstimateDtos; import common.ecommerce.hengjian.dto.HengjianInventoryDtos; import common.ecommerce.hengjian.dto.HengjianInboundCreateDtos; import common.ecommerce.hengjian.dto.HengjianInboundQueryDtos; import common.ecommerce.hengjian.dto.HengjianInventoryMovementDtos; import common.ecommerce.hengjian.dto.HengjianReturnDetailDtos; import common.ecommerce.hengjian.dto.HengjianReturnHandleDtos; import common.ecommerce.hengjian.dto.HengjianReturnListDtos; import common.ecommerce.hengjian.dto.HengjianReturnPlanCreateDtos; import common.ecommerce.hengjian.dto.HengjianTransferDtos; import common.ecommerce.hengjian.dto.HengjianOperationFeeDtos; import common.ecommerce.hengjian.dto.HengjianOrderDetailDtos; import common.ecommerce.hengjian.dto.HengjianOrderAttachmentDtos; import common.ecommerce.hengjian.dto.HengjianOrderListDtos; import common.ecommerce.hengjian.dto.HengjianProductQueryDtos; import common.ecommerce.hengjian.dto.HengjianProductSaveDtos; import common.ecommerce.hengjian.dto.HengjianStorageFeeDtos; import common.ecommerce.hengjian.dto.HengjianTailDeliveryFeeDtos; import common.ecommerce.hengjian.dto.HengjianTrackingChangeDtos; import common.ecommerce.hengjian.dto.HengjianTrackingChangeQueryDtos; import common.ecommerce.hengjian.dto.HengjianWarehouseDtos; import common.ecommerce.hengjian.HengjianConstants; import common.ecommerce.hengjian.http.HengjianEnvelope; import common.ecommerce.hengjian.http.HengjianRateLimiter; import common.ecommerce.hengjian.http.HengjianRequestFactory; import common.ecommerce.http.HttpRequest; import common.ecommerce.http.HttpResponse; import common.ecommerce.http.HttpTransport; import common.ecommerce.http.JacksonJsonCodec; import common.ecommerce.shared.error.PlatformBusinessException; import common.ecommerce.shared.support.Page; import common.ecommerce.warehouse.capability.AddressClassificationCapable; import common.ecommerce.warehouse.capability.DestructionCapable; import common.ecommerce.warehouse.capability.InboundCapable; import common.ecommerce.warehouse.capability.InventoryCapable; import common.ecommerce.warehouse.capability.TransferCapable; import common.ecommerce.warehouse.capability.WarehouseReturnCapable; import common.ecommerce.warehouse.capability.LogisticsProductCapable; import common.ecommerce.warehouse.capability.OutboundCapable; import common.ecommerce.warehouse.capability.TrackingChangeCapable; import common.ecommerce.warehouse.capability.WarehouseDirectoryCapable; import common.ecommerce.warehouse.capability.WarehouseFeeCapable; import common.ecommerce.warehouse.capability.WarehouseFeeEstimateCapable; import common.ecommerce.warehouse.capability.WarehouseProductCapable; import common.ecommerce.warehouse.enums.AddressType; import common.ecommerce.warehouse.enums.CancelEligibility; import common.ecommerce.warehouse.enums.InventorySyncStrategy; import common.ecommerce.warehouse.enums.ReturnStatus; import common.ecommerce.warehouse.enums.LabelMode; import common.ecommerce.warehouse.enums.TrackingChangeHandleType; import common.ecommerce.warehouse.enums.WarehouseCapability; import common.ecommerce.warehouse.enums.SortDirection; import common.ecommerce.warehouse.enums.WarehouseFeeType; import common.ecommerce.warehouse.enums.WarehouseProvider; import common.ecommerce.warehouse.error.OutboundCancelBlockedException; import common.ecommerce.warehouse.error.WarehouseException; import common.ecommerce.warehouse.model.BillingDocument; import common.ecommerce.warehouse.model.CancelCommand; import common.ecommerce.warehouse.model.BoxLabelCommand; import common.ecommerce.warehouse.model.DestructionCommand; import common.ecommerce.warehouse.model.DestructionOrder; import common.ecommerce.warehouse.model.CancelResult; import common.ecommerce.warehouse.model.FeeEstimateQuery; import common.ecommerce.warehouse.model.FeeEstimateResult; import common.ecommerce.warehouse.model.FeeQuery; import common.ecommerce.warehouse.model.InboundCommand; import common.ecommerce.warehouse.model.InboundOrder; import common.ecommerce.warehouse.model.InboundQuery; import common.ecommerce.warehouse.model.InboundReceipt; import common.ecommerce.warehouse.model.InventoryMovement; import common.ecommerce.warehouse.model.LabelPrintTask; import common.ecommerce.warehouse.model.InventoryMovementQuery; import common.ecommerce.warehouse.model.InventoryQuery; import common.ecommerce.warehouse.model.InventorySnapshot; import common.ecommerce.warehouse.model.TransferCommand; import common.ecommerce.warehouse.model.TransferOrder; import common.ecommerce.warehouse.model.ReturnCommand; import common.ecommerce.warehouse.model.ReturnHandle; import common.ecommerce.warehouse.model.ReturnProcessCommand; import common.ecommerce.warehouse.model.ReturnQuery; import common.ecommerce.warehouse.model.TransferQuery; import common.ecommerce.warehouse.model.WarehouseAttachment; import common.ecommerce.warehouse.model.WarehouseReturn; import common.ecommerce.warehouse.model.LogisticsProduct; import common.ecommerce.warehouse.model.OutboundCommand; import common.ecommerce.warehouse.model.OutboundOrder; import common.ecommerce.warehouse.model.OutboundQuery; import common.ecommerce.warehouse.capability.WarehouseProduct; import common.ecommerce.warehouse.model.ProductInfo; import common.ecommerce.warehouse.model.ProductQuery; import common.ecommerce.warehouse.model.OutboundReceipt; import common.ecommerce.warehouse.model.OutboundRef; import common.ecommerce.warehouse.model.PackageResult; import common.ecommerce.warehouse.model.TrackingChangeCommand; import common.ecommerce.warehouse.model.TrackingChangeOrder; import common.ecommerce.warehouse.model.WarehouseFacility; import common.ecommerce.warehouse.sdk.WarehouseContext; import java.time.ZoneOffset; import java.util.ArrayList; import java.util.EnumSet; import java.util.Iterator; import java.util.LinkedHashMap; import java.util.List; import java.util.Map; /** * 恒健适配器。 * *
已接入:仓库目录、承运商 / 物流产品、按仓的物流渠道(只读), * 以及商品创建 / 编辑({@code /v1/product/save},保存语义)。
* *出库 / 库存 / 入库 / 退货等接口尚未接入,能力位不声明: * 门面调用会显式抛 {@code WarehouseUnsupportedCapabilityException},不返回空集合。
* *适配器只持有协议与基础设施,不持有端点与凭据——两者随每次调用经 * {@code WarehouseConnection} 传入。
*/ public final class HengjianAdapter implements WarehouseDirectoryCapable, LogisticsProductCapable, WarehouseProductCapable, OutboundCapable, TrackingChangeCapable, WarehouseFeeCapable, WarehouseFeeEstimateCapable, AddressClassificationCapable, InventoryCapable, InboundCapable, TransferCapable, WarehouseReturnCapable, DestructionCapable { private static final String OP_WAREHOUSE_LIST = "warehouse.directory.warehouses"; private static final String OP_CARRIERS = "warehouse.directory.carriers"; private static final String OP_LOGISTICS_PRODUCTS = "warehouse.logistics.products"; private static final String OP_PRODUCT_SAVE = "warehouse.product.create"; private static final String OP_PRODUCT_QUERY = "warehouse.product.query"; private static final String OP_ORDER_CREATE = "warehouse.outbound.create"; private static final String OP_ORDER_GET = "warehouse.outbound.get"; private static final String OP_ORDER_QUERY = "warehouse.outbound.query"; private static final String OP_ORDER_CANCEL = "warehouse.outbound.cancel"; private static final String OP_ORDER_ATTACHMENT = "warehouse.outbound.attachment"; private static final String OP_TRACKING_CHANGE_CREATE = "warehouse.tracking.change.create"; private static final String OP_TRACKING_CHANGE_GET = "warehouse.tracking.change.get"; private static final String OP_FEE_STORAGE = "warehouse.fee.storage"; private static final String OP_FEE_TAIL_DELIVERY = "warehouse.fee.tailDelivery"; private static final String OP_FEE_OPERATION = "warehouse.fee.operation"; private static final String OP_FEE_ESTIMATE = "warehouse.fee.estimate"; private static final String OP_ADDRESS_CLASSIFY = "warehouse.address.classify"; private static final String OP_INVENTORY_QUERY = "warehouse.inventory.query"; private static final String OP_INVENTORY_MOVEMENTS = "warehouse.inventory.movements"; private static final String OP_INBOUND_CREATE = "warehouse.inbound.create"; private static final String OP_INBOUND_GET = "warehouse.inbound.get"; private static final String OP_INBOUND_QUERY = "warehouse.inbound.query"; private static final String OP_INBOUND_BOX_LABEL = "warehouse.inbound.boxLabel"; private static final String OP_TRANSFER_CREATE = "warehouse.transfer.create"; private static final String OP_TRANSFER_QUERY = "warehouse.transfer.query"; private static final String OP_TRANSFER_CANCEL = "warehouse.transfer.cancel"; private static final String OP_RETURN_CREATE = "warehouse.return.create"; private static final String OP_DESTRUCTION_CREATE = "warehouse.destruction.create"; private static final String OP_DESTRUCTION_GET = "warehouse.destruction.get"; private static final String OP_RETURN_GET = "warehouse.return.get"; private static final String OP_RETURN_QUERY = "warehouse.return.query"; /** 退货列表的时间窗格式(恒健文档:{@code yyyy-MM-dd HH:mm:ss},UTC)。 */ private static final java.time.format.DateTimeFormatter HENGJIAN_TIME = java.time.format.DateTimeFormatter.ofPattern("yyyy-MM-dd HH:mm:ss"); /** 恒健 {@code queryType}:来源单号。 */ private static final String QUERY_TYPE_SOURCE_NO = "2"; /** 恒健 {@code queryType}:退货 tracking。 */ private static final String QUERY_TYPE_TRACKING = "4"; private static final String OP_RETURN_HANDLES = "warehouse.return.handles"; private static final String OP_RETURN_PROCESS = "warehouse.return.process"; /** 退货列表默认页大小(文档没写,按同站惯例 100)。 */ private static final int PAGE_SIZE_DEFAULT = 100; /** 退货处理单列表默认页大小(文档写默认 20)。 */ private static final int HANDLE_PAGE_SIZE_DEFAULT = 20; /** 保存语义没有 create / update 之分,仓方也不回是哪种。 */ private static final String SAVED = "SAVED"; private final HttpTransport transport; private final JacksonJsonCodec json; private final HengjianRequestFactory requestFactory; private final HengjianRateLimiter rateLimiter; public HengjianAdapter(HttpTransport transport, JacksonJsonCodec json) { this.transport = transport; this.json = json; this.requestFactory = new HengjianRequestFactory(json); this.rateLimiter = new HengjianRateLimiter(); } @Override public String adapterId() { return HengjianConstants.ADAPTER_ID; } @Override public WarehouseProvider provider() { return WarehouseProvider.HENGJIAN; } /** 默认连生产环境;联调请在账户上配置 {@code endpointBaseUrl} 覆盖。 */ @Override public String defaultEndpointBaseUrl() { return common.ecommerce.hengjian.HengjianConstants.PRODUCTION_BASE_URL; } @Override public EnumSet⚠ 路径未真机确认,见 {@link HengjianConstants#PATH_DESTRUCTION_CREATE}。
* *响应无 data:只有 {@code code / message},不回仓单号也不回状态。 * 所以 {@code providerDestructionId} 与 {@code status} 都留 null——不拿来源单号冒充仓单号, * 也不把「已提交」当「已执行」。
*/ @Override public DestructionOrder create(WarehouseContext ctx, DestructionCommand cmd) { String warehouseCode = HengjianOutboundMapper.resolveWarehouseCode( cmd.warehouseId(), ctx.providerWarehouseId()); HengjianDestructionDtos.CreateRequest body = HengjianDestructionMapper.toRequest(cmd, warehouseCode); execute(ctx, HengjianConstants.PATH_DESTRUCTION_CREATE, body, OP_DESTRUCTION_CREATE); return HengjianDestructionMapper.toCreated(cmd, warehouseCode); } /** * 查销毁计划({@code POST /v2/destroyPlanOrder/find})。 * *⚠ 路径未真机确认,见 {@link HengjianConstants#PATH_DESTRUCTION_FIND}。
* *请求体是裸数组;响应 {@code data} 也是数组,查不到的单号不返回 * (不是返回空对象)。这里只查一个单号,返回匹配的那条,没有则 null。
*/ @Override public DestructionOrder getDestruction(WarehouseContext ctx, String destructionNo) { List承接门面的幂等守卫(键 {@code warehouseCode + returnRequestNo + create})。
* *请求是双层包裹(业务字段在 {@code params} 下),与其它接口不同。
* *响应只回头级信息,不回明细行——需要明细要再查详情。
*/ @Override public WarehouseReturn create(WarehouseContext ctx, ReturnCommand cmd) { String warehouseCode = HengjianOutboundMapper.resolveWarehouseCode( cmd.warehouseId(), ctx.providerWarehouseId()); HengjianReturnPlanCreateDtos.SaveRequest body = HengjianReturnMapper.toRequest(cmd, warehouseCode); String raw = execute(ctx, HengjianConstants.PATH_RETURN_PLAN_CREATE, body, OP_RETURN_CREATE); HengjianReturnPlanCreateDtos.SaveResponse resp = json.fromJson(raw, HengjianReturnPlanCreateDtos.SaveResponse.class); if (resp == null || resp.data == null || trimToNull(resp.data.returnPlanNo) == null) { // 拿不到仓侧计划单号不能当成功:后续查询 / 处理方式都要它 throw WarehouseException.builder() .message("hengjian return plan returned no returnPlanNo: " + safeRelay(raw)) .operation(OP_RETURN_CREATE) .warehouseCode(ctx.warehouseCode()) .provider(provider().name()) .requestId(ctx.requestId()) .retryable(false) .rawResponse(safeRelay(raw)) .build(); } return HengjianReturnMapper.toCreated(cmd, resp.data); } /** * 查退货计划详情({@code POST /v1/saleReturn/thirdParty/getReturnPlanOrderInfo})。 * *请求是双层包裹({@code {"params":{"orderNo"}}})。单号既可是计划单号, * 也可是来源单号——详情响应同时回 {@code returnPlanNo} 与 {@code sourceOrderNo}。
* *查不到({@code data} 为空)返回 null。
*/ @Override public WarehouseReturn getReturn(WarehouseContext ctx, String returnRequestNo) { String orderNo = trimToNull(returnRequestNo); if (orderNo == null) { throw new IllegalArgumentException("hengjian return detail requires an order number"); } HengjianReturnDetailDtos.DetailRequest body = HengjianReturnQueryMapper.toDetailRequest(orderNo); String raw = execute(ctx, HengjianConstants.PATH_RETURN_PLAN_DETAIL, body, OP_RETURN_GET); JsonNode data = json.nodeAt(raw, "data"); if (data == null || data.isNull() || data.isMissingNode()) { return null; } HengjianReturnDetailDtos.PlanDetail detail = json.fromJson(data.toString(), HengjianReturnDetailDtos.PlanDetail.class); return HengjianReturnQueryMapper.toReturn(detail); } /** * 分页查退货计划({@code POST /v1/saleReturn/thirdParty/getReturnPlanOrderPage})。 * *支持的维度见 {@link ReturnQuery};不支持的维度直接拒绝, * 静默忽略会让调用方以为筛过。
* *恒健的三处限制:
*请求是平铺的(无 {@code params} 包裹),与 thirdParty 那两个不同。
* *恒健没有对应的统一模型:这里返回仓方的处理单行,供宿主填写处理方式与回收照片。
*/ @Override public Page请求是平铺的(无 {@code params} 包裹),与 thirdParty 那两个不同。
*/ public Page请求平铺,用 {@code returnPlanNo + returnNo + erpSku + tracking} 四项定位, * 不用行 id——与运去哪的条目处理接口不同。
* *两级处理方式:{@code handlingMethod}(1 继续拍照 / 2 处理方式)是开关, * {@code primaryHandlingMethod}(101~206)是具体动作。core 的 * {@code ReturnProcessDisposition} 只有部分能映射(销毁 / 上架良品 / 换标上架 / 卖家自提), * 拍照类与重新包装必须显式给原值。
*/ @Override public void process(WarehouseContext ctx, ReturnProcessCommand cmd) { HengjianReturnHandleDtos.HandlingMethodRequest body = HengjianReturnQueryMapper.toHandlingMethodRequest(cmd); execute(ctx, HengjianConstants.PATH_RETURN_HANDLING_METHOD, body, OP_RETURN_PROCESS); } // ------------------------------------------------------------------ 调拨 /** * 创建调拨计划({@code POST /v1/transferPlan/create})。 * *真机确认必填:调出 / 调入仓、期望出库 / 入库时间。 * 响应 {@code data} 是字符串单号(不是对象)。
* *外部仓库用仓代码 {@code Other} 表达——恒健的约定,适配器不猜。
*/ @Override public TransferOrder create(WarehouseContext ctx, TransferCommand cmd) { HengjianTransferDtos.CreateRequest body = HengjianTransferMapper.toRequest(cmd); String raw = execute(ctx, HengjianConstants.PATH_TRANSFER_CREATE, body, OP_TRANSFER_CREATE); String planNo = json.stringAt(raw, "data"); if (trimToNull(planNo) == null) { // 拿不到单号不能当成功:后续查询 / 取消都要它 throw WarehouseException.builder() .message("hengjian transfer returned no data (plan no): " + safeRelay(raw)) .operation(OP_TRANSFER_CREATE) .warehouseCode(ctx.warehouseCode()) .provider(provider().name()) .requestId(ctx.requestId()) .retryable(false) .rawResponse(safeRelay(raw)) .build(); } return HengjianTransferMapper.toCreated(cmd, planNo.trim()); } /** * 多条件分页查调拨计划({@code GET /v1/transferPlan/findByPage})。 * *恒健的过滤参数都是单值(不是数组),所以统一模型里给了多个单号时 * 只下发第一个——这与其它接口「拒绝多值」的做法不同,因为这里的语义是 * 「按这个单号查」,多给没有意义。文档已注明。
*/ @Override public Page这是统一模型里 {@link TransferCapable#deleteTransfer} 的落点:恒健叫「取消」, * 语义等价于「撤销这张调拨单」。取消要收费是运去哪的概念,恒健没有。
* *参数在 query(不是 body);真机确认 {@code sourceNo} 必填。
*/ @Override public void deleteTransfer(WarehouseContext ctx, String providerTransferNo) { String sourceNo = trimToNull(providerTransferNo); if (sourceNo == null) { throw new IllegalArgumentException("hengjian transfer cancel requires sourceNo"); } Map承接门面的幂等守卫(键 {@code warehouseCode + inboundRequestNo + create})。
* *响应不回仓单号:只有 {@code code / message}。所以 * {@code providerInboundId} 为 null——后续查详情 / 取消只能用来源单号。 * 这里不把来源单号冒充仓单号填进去。
* *{@code status=0} 是草稿,草稿状态下再调本接口是更新而非新建。 * 由调用方经 {@code InboundCommand.documentStatus()} 决定,适配器不猜。
*/ @Override public InboundReceipt create(WarehouseContext ctx, InboundCommand cmd) { String warehouseCode = HengjianOutboundMapper.resolveWarehouseCode( cmd.warehouseId(), ctx.providerWarehouseId()); HengjianInboundCreateDtos.CreateRequest body = HengjianInboundMapper.toRequest(cmd, warehouseCode); execute(ctx, HengjianConstants.PATH_INBOUND_CREATE, body, OP_INBOUND_CREATE); // 仓方不回单号:保持 null,不拿来源单号顶替 return InboundReceipt.of(cmd.inboundRequestNo(), null); } /** * 查入库计划详情({@code POST /v1/inbound/getInboundPlanInfo})。 * *恒健只按单号查,且这个单号可以是仓方计划单号,也可以是来源单号 * (详情响应同时回 {@code inboundPlanOrderNo} 与 {@code sourceNo})。
* *查不到({@code data} 为空)返回 null——与其它仓一致。
*/ @Override public InboundOrder get(WarehouseContext ctx, String inboundRef) { String orderNo = trimToNull(inboundRef); if (orderNo == null) { throw new IllegalArgumentException("hengjian inbound get requires an order number"); } HengjianInboundQueryDtos.FindOneRequest body = HengjianInboundQueryMapper.toFindOneRequest(orderNo); String raw = execute(ctx, HengjianConstants.PATH_INBOUND_GET, body, OP_INBOUND_GET); JsonNode data = json.nodeAt(raw, "data"); if (data == null || data.isNull() || data.isMissingNode()) { return null; } HengjianInboundQueryDtos.InboundPlan plan = json.fromJson(data.toString(), HengjianInboundQueryDtos.InboundPlan.class); return HengjianInboundQueryMapper.toOrder(plan, fallbackWarehouse(ctx)); } /** * 生成入库箱标({@code POST /v2/inbound/boxLabelGenerate})。 * *响应没有任务号也没有文件:只有 {@code code / message}。 * 文件要从入库计划详情的 {@code packingLabelUrl} 取,所以返回的 * {@link LabelPrintTask#taskNo()} 为 null——不代表调用失败。
* *恒健要求 {@code isIndexNo} / {@code isOriginCountry} 必填,统一模型里是 * null-able;没给时本地拒绝而不是猜一个值(猜错会多印或漏印一行)。
* *尺寸 / 每页数量的联动约束由 {@link BoxLabelCommand} 构造期校验; * 恒健没有 {@code sizeType} / {@code downloadMode} 口径,改用 {@code paperType}。
*/ @Override public LabelPrintTask printBoxLabel(WarehouseContext ctx, BoxLabelCommand cmd) { String fallback = trimToNull(ctx.providerWarehouseId()); if (fallback == null) { fallback = trimToNull(cmd.inboundRequestNo()); } HengjianBoxLabelDtos.BoxLabelRequest body = HengjianBoxLabelMapper.toRequest(cmd, fallback); execute(ctx, HengjianConstants.PATH_INBOUND_BOX_LABEL, body, OP_INBOUND_BOX_LABEL); return HengjianBoxLabelMapper.toTask(cmd, fallback); } /** * 按游标分页查入库单。 * *统一模型这个入口只有一个游标,恒健的列表接口支持多条件;这里把游标当页码, * 其余条件为空——需要按状态 / 时间窗筛时用 * {@link #queryInbounds(WarehouseContext, InboundQuery)}。
*/ @Override public Page恒健列表支持的维度:仓 / 计划单号 / 来源单号 / 状态码 / 库存类型 / * 七种时间区间(创建 / 更新 / 完成 / 期望到货 / 预计发货 / 预计入库 / 首次接收)/ * Amazon shipmentId。
* *统一模型只表达其中三种时间窗(创建 / 更新 / 完成)。其余四种恒健独有, * 模型里没有——需要时再经 {@code InboundQuery} 扩字段,不在这里硬塞。
* *未支持的维度直接拒绝:见 {@link #queryInbounds} 里的校验。
*/ @Override public Page恒健的两个库存接口都不支持按更新时间增量:按 SKU 的全量返回、 * 按仓的分页返回,都没有 {@code updatedAfter} 入参。所以策略是 * {@link InventorySyncStrategy#FULL_PULL_DIFF}——宿主全量拉后自己做差异比对。
* *流水接口({@code movements})能按日期查,但那是变动明细, * 不是余额,不能拿来重建当前库存。
*/ @Override public InventorySyncStrategy syncStrategy() { return InventorySyncStrategy.FULL_PULL_DIFF; } /** * 查库存。 * *恒健有两个接口,统一模型只有一个方法,按「给了什么」分流:
*两者都给的场景(按仓 + SKU 过滤)恒健没有对应接口,本地拒绝—— * 静默丢掉一个条件会让调用方以为过滤生效了。
* *{@code updatedAfter} 恒健不支持,传了就拒绝(同上理由)。
*/ @Override public Page真机确认:SKU 与日期区间都必填,区间 ≤ 30 个自然日,rows 1~100。
*/ @Override public Page统一模型是 cm / g,恒健也接受 {@code cm} / {@code g},不换算; * 但它的包裹尺寸字段是 INTEGER,所以厘米值四舍五入取整(截断会让报价偏低)。
* *恒健不按仓维度返回报价,结果只有一个实例, * {@code shipOrgWarehouseCode} 用账户仓填充。
*/ @Override public List真机确认五项必填({@code street1 / zip / city / state / country}), * 缺任何一项仓方都回参数校验异常,所以本地先挡。
*/ @Override public AddressType classifyAddress(WarehouseContext ctx, String street1, String street2, String city, String state, String postal, String country) { String s1 = requireAddressPart(street1, "street1"); String c = requireAddressPart(city, "city"); String st = requireAddressPart(state, "state"); String zip = requireAddressPart(postal, "postal"); String cy = requireAddressPart(country, "country"); HengjianAddressClassificationDtos.ClassifyRequest body = HengjianEstimateMapper.toClassifyRequest(s1, street2, c, st, zip, cy); String raw = execute(ctx, HengjianConstants.PATH_ADDRESS_CLASSIFICATION, body, OP_ADDRESS_CLASSIFY); HengjianAddressClassificationDtos.ClassifyResponse resp = json.fromJson(raw, HengjianAddressClassificationDtos.ClassifyResponse.class); return HengjianEstimateMapper.addressTypeOf(resp == null ? null : resp.data); } private static String requireAddressPart(String value, String field) { String v = trimToNull(value); if (v == null) { throw new IllegalArgumentException( "hengjian address classification requires " + field); } return v; } // ------------------------------------------------------------------ 计费明细 /** * 拉取计费明细(仓储费 / 尾程费 / 作业费)。 * *恒健把三类费用拆成三个独立接口,行字段各不相同,统一模型只有一个 * {@code settlements()}。因此必须由调用方用 {@link FeeQuery#costType()} 指定查哪一类:
* *| costType | 接口 |
|---|---|
| {@code STORAGE} | {@code getChargingStorageSettlement} |
| {@code LAST_MILE} | {@code getChargingTailDeliverySettlement} |
| {@code OPERATION} | {@code getChargingOperationSettlement} |
不指定就拒绝而不是「三个都查再合并」:三类费用的行结构不同、金额口径也不同, * 合并会让调用方以为拿到了一份完整账单,实际少了另外两类。
* *{@code VALUE_ADDED}(增值服务费)恒健没有对应接口,显式拒绝。
* *三个接口都是分页的,统一方法返回 {@code List}、不带游标,所以分页由调用方驱动: * 用 {@link FeeQuery#toBuilder()}{@code .pageCursor("2")} 翻页。 * 判末页的约定:返回条数小于本次请求的 {@code pageSize} 即末页 * (少于请求量说明后面没有了)。
*/ @Override public List承接门面的幂等守卫(键 {@code warehouseCode + changeRequestNo + create}); * 这里只负责拼报文与解析。
* *真机确认的必填项(文档标错 / 漏标):{@code trackingNo}、{@code orderNo}、 * {@code remark}、{@code handleType};换址(2)还要新收件人三项。 * 仓方还会校验「来源单号与 trackingNo 属于同一张单」——这一条本地挡不住, * 只能在真机联调时保证调用方给的是一对真实存在的单号 + 运单号。
* *响应只回 {@code trackingChangeOrderNo},没有状态——创建成功只代表申请已提交, * 承运商是否受理要看 subsequent 查询。
*/ @Override public TrackingChangeOrder createChange(WarehouseContext ctx, TrackingChangeCommand cmd) { HengjianTrackingChangeDtos.CreateRequest body = toCreateRequest(cmd); String raw = execute(ctx, HengjianConstants.PATH_TRACKING_CHANGE_CREATE, body, OP_TRACKING_CHANGE_CREATE); HengjianTrackingChangeDtos.CreateResponse resp = json.fromJson(raw, HengjianTrackingChangeDtos.CreateResponse.class); if (resp == null || resp.data == null || trimToNull(resp.data.trackingChangeOrderNo) == null) { throw WarehouseException.builder() .message("hengjian tracking change returned no trackingChangeOrderNo: " + safeRelay(raw)) .operation(OP_TRACKING_CHANGE_CREATE) .warehouseCode(ctx.warehouseCode()) .provider(provider().name()) .requestId(ctx.requestId()) .retryable(false) .rawResponse(safeRelay(raw)) .build(); } return TrackingChangeOrder.builder() .changeRequestNo(cmd.changeRequestNo()) .providerChangeOrderNo(resp.data.trackingChangeOrderNo.trim()) .sourceProvider(provider()) .warehouseCode(ctx.warehouseCode()) .trackingNumber(cmd.trackingNumber()) .orderNo(trimToNull(cmd.orderNo())) .handleType(cmd.handleType()) // 创建接口不回状态:保持 null,不拿请求侧的值冒充仓方状态 .build(); } /** * 查询物流异动单({@code POST /v1/trackingChange/findOrder})。 * *路径与文档不同:文档写 {@code /v1/saleOrder/findOrder},真机 404; * 正确路径在 {@link HengjianConstants#PATH_TRACKING_CHANGE_FIND}。
*/ @Override public TrackingChangeOrder getChange(WarehouseContext ctx, String providerChangeOrderNo) { String changeNo = trimToNull(providerChangeOrderNo); if (changeNo == null) { throw new IllegalArgumentException("providerChangeOrderNo must not be blank"); } HengjianTrackingChangeQueryDtos.FindOrderRequest body = new HengjianTrackingChangeQueryDtos.FindOrderRequest(); body.trackingChangeOrderNo = changeNo; String raw = execute(ctx, HengjianConstants.PATH_TRACKING_CHANGE_FIND, body, OP_TRACKING_CHANGE_GET); JsonNode data = json.nodeAt(raw, "data"); if (data == null || data.isNull() || data.isMissingNode()) { return null; } HengjianTrackingChangeQueryDtos.TrackingChangeDetail detail = json.fromJson(data.toString(), HengjianTrackingChangeQueryDtos.TrackingChangeDetail.class); return HengjianTrackingChangeMapper.toOrder(detail, ctx.warehouseCode(), provider()); } /** 统一命令 → 恒健请求;必填项在本地校验。 */ static HengjianTrackingChangeDtos.CreateRequest toCreateRequest(TrackingChangeCommand cmd) { String trackingNo = requireText(cmd.trackingNumber(), "trackingNumber", cmd.changeRequestNo()); String orderNo = requireText(cmd.orderNo(), "orderNo", cmd.changeRequestNo()); String remark = requireText(cmd.remark(), "remark", cmd.changeRequestNo()); int handleType = handleTypeOf(cmd.handleType()); HengjianTrackingChangeDtos.CreateRequest body = new HengjianTrackingChangeDtos.CreateRequest(); body.trackingNo = trackingNo; body.orderNo = orderNo; body.remark = remark; body.handleType = handleType; if (cmd.handleType() == TrackingChangeHandleType.ADDRESS_CHANGE) { // 换址三项真机必填,缺任一项仓方都会拒;本地先说清楚缺哪个 body.newRecipientName = requireText(cmd.newRecipientName(), "newRecipientName", cmd.changeRequestNo()); body.newRecipientPhone = requireText(cmd.newRecipientPhone(), "newRecipientPhone", cmd.changeRequestNo()); body.newRecipientAddress = requireText(cmd.newRecipientAddress(), "newRecipientAddress", cmd.changeRequestNo()); } return body; } /** 核心枚举 → 恒健 handleType:1 召回 / 2 换址 / 3 在途异常。 */ static int handleTypeOf(TrackingChangeHandleType type) { if (type == null) { throw new IllegalArgumentException("handleType must not be null"); } switch (type) { case RECALL: return 1; case ADDRESS_CHANGE: return 2; case IN_TRANSIT_EXCEPTION: return 3; default: throw new IllegalArgumentException("unsupported handleType: " + type); } } private static String requireText(String value, String field, String changeRequestNo) { String v = trimToNull(value); if (v == null) { throw new IllegalArgumentException("hengjian tracking change " + changeRequestNo + " requires " + field + " (恒健必填)"); } return v; } // ------------------------------------------------------------------ 出库 /** * 创建销售发货单({@code POST /v1/saleOrder/create})。 * *承接 {@code WarehouseOutbounds.create} 的幂等守卫:同一 * {@code outboundRequestNo} 重复下发由门面拦住,这里只负责拼报文与解析。
* *响应只回 {@code data.orderId}(仓内部数字 id,不是字符串单号)。 * 恒健的取消接口同时要 {@code orderId} 与 {@code orderNo},所以这个 id * 必须随 {@link OutboundReceipt#providerOrderId()} 落库;缺了它后续取消做不了, * 因此拿不到就报错,不静默当成创建成功。
*/ @Override public OutboundReceipt create(WarehouseContext ctx, OutboundCommand cmd) { requirePlatformLabelSupported(cmd); String warehouseCode = HengjianOutboundMapper.resolveWarehouseCode( cmd.warehouseId(), ctx.providerWarehouseId()); HengjianCreateOrderDtos.CreateOrderRequest body = HengjianOutboundMapper.toRequest(cmd, warehouseCode, ctx.clock()); String raw = execute(ctx, HengjianConstants.PATH_ORDER_CREATE, body, OP_ORDER_CREATE); HengjianCreateOrderDtos.CreateOrderResponse resp = json.fromJson(raw, HengjianCreateOrderDtos.CreateOrderResponse.class); if (resp == null || resp.data == null || resp.data.orderId == null) { throw WarehouseException.builder() .message("hengjian create order returned no data.orderId: " + safeRelay(raw)) .operation(OP_ORDER_CREATE) .warehouseCode(ctx.warehouseCode()) .provider(provider().name()) .requestId(ctx.requestId()) .retryable(false) .rawResponse(safeRelay(raw)) .build(); } return OutboundReceipt.of(cmd.outboundRequestNo(), String.valueOf(resp.data.orderId), resp.message); } /** * 查订单详情({@code POST /v1/saleOrder/findOne})。 * *恒健只按来源单号查。统一引用里的 {@code outboundRequestNo} 就是来源单号; * {@code providerOrderId} 是仓内部数字 id,这个接口查不了,所以拿来当兜底 * (调用方只给了 id 时照样发出去,仓方会查不到,由仓方报错而不是我们静默返回 null)。
* *查不到({@code data} 为空)返回 null——与其它仓一致,调用方据此判断「没有这单」。
*/ @Override public OutboundOrder get(WarehouseContext ctx, OutboundRef ref) { String orderNo = orderNoOf(ref); HengjianOrderDetailDtos.FindOneRequest body = new HengjianOrderDetailDtos.FindOneRequest(); body.orderNo = orderNo; String raw = execute(ctx, HengjianConstants.PATH_ORDER_FIND_ONE, body, OP_ORDER_GET); JsonNode data = json.nodeAt(raw, "data"); if (data == null || data.isNull() || data.isMissingNode()) { return null; } HengjianOrderDetailDtos.OrderDetail detail = json.fromJson(data.toString(), HengjianOrderDetailDtos.OrderDetail.class); return HengjianOrderMapper.toOrder(detail, ctx.providerWarehouseId()); } /** * 查订单列表({@code GET /v1/saleOrder/findByPage})。 * *恒健要求「时间、订单号、订单 id 三者必填其一」,所以:
*时间跨度上限 30 天,超过也在本地拒绝。
* *{@code orderRef}(平台单号)恒健没有对应查询参数,不参与查询; * {@code statuses} 恒健列表也没有状态过滤参数,传了就拒绝——静默忽略会让调用方 * 以为过滤生效了。
*/ @Override public Page请求平铺(无 {@code params} 包裹)。响应无 data,只有 {@code code / message}, * 所以本方法无返回值。
* *恒健要求每行 {@code name} / {@code type} 必填、{@code url} 与 {@code file} 二选一; * 缺了本地拒绝,不把半成品发出去。
*/ @Override public void uploadAttachments(WarehouseContext ctx, OutboundRef ref, List认不出的值拒绝,不猜——发错类型会让仓方把面单当「其他」存。
*/ private static Integer parseAttachType(String raw, String name) { try { int value = Integer.parseInt(raw.trim()); if (value < 0 || value > 6) { throw new IllegalArgumentException( "hengjian attachment type for " + name + " must be 0-6, got " + value); } return value; } catch (NumberFormatException e) { // 部分仓用词表(Shippinglabel / BOL 等);恒健这里只收数字 throw new IllegalArgumentException( "hengjian attachment type for " + name + " must be an integer 0-6, got " + raw); } } /** * 取消资格预判:查详情按状态推断。 * *恒健没有独立的取消预判接口。已发货 / 已取消 / 已退款 / 已删除不再接受取消, * 判为 {@link CancelEligibility#BLOCKED};其余交给取消时仓方判定。
* *查不到单时返回 BLOCKED,不猜 FREE——猜错会下发出一个注定被拒的取消。
*/ @Override public CancelEligibility checkCancel(WarehouseContext ctx, OutboundRef ref) { OutboundOrder order = get(ctx, ref); if (order == null) { return CancelEligibility.BLOCKED; } switch (order.status()) { case SHIPPED: case CANCELLED: case REFUNDED: case DELETED: case UNKNOWN: // UNKNOWN 也判 BLOCKED:恒健的状态词表将来可能加值, // 认不出时不该凭猜下发取消 return CancelEligibility.BLOCKED; default: return CancelEligibility.FREE; } } /** * 取消订单({@code POST /v1/saleOrder/cancel})。 * *恒健要求 {@code orderId} 与 {@code orderNo} 两个都传,而统一模型的 * {@link CancelCommand} 允许只给其中一个。约定:
*缺哪个就用已知的那个去列表接口补一次——这是拿到 {@code orderId} 的正规途径 * (详情接口不回它)。补不到(仓里没有这张单)直接报参数错误, * 不发必然被仓方拒的取消请求。
* *恒健没有取消费概念,{@link CancelCommand#acceptCharge()} 在这里不生效。 * 仓方拒绝取消时抛 {@link OutboundCancelBlockedException},与参数错误区分开。
*/ @Override public CancelResult cancel(WarehouseContext ctx, CancelCommand cmd) { String orderNo = trimToNull(cmd.outboundRequestNo()); Long orderId = parseOrderId(cmd.providerOrderId()); if (orderNo == null && orderId == null) { throw new IllegalArgumentException( "hengjian needs outboundRequestNo or providerOrderId to cancel an order"); } if (orderNo == null || orderId == null) { HengjianOrderListDtos.OrderRow row = findRow(ctx, orderNo, orderId); if (row == null) { throw validation(ctx, OP_ORDER_CANCEL, "hengjian order not found, cannot resolve " + (orderNo == null ? "orderNo" : "orderId") + " for " + (orderNo != null ? orderNo : String.valueOf(orderId))); } if (orderNo == null) { orderNo = trimToNull(row.orderNo); } if (orderId == null && row.orderId != null) { orderId = row.orderId; } } if (orderNo == null || orderId == null) { throw validation(ctx, OP_ORDER_CANCEL, "hengjian cancel requires both orderId and orderNo; " + "could not resolve " + (orderNo == null ? "orderNo" : "orderId")); } HengjianCancelOrderDtos.CancelOrderRequest body = new HengjianCancelOrderDtos.CancelOrderRequest(); body.orderId = orderId; body.orderNo = orderNo; String raw; try { raw = execute(ctx, HengjianConstants.PATH_ORDER_CANCEL, body, OP_ORDER_CANCEL); } catch (PlatformBusinessException e) { // 取消失败只有 message,无法细分原因;取消场景统一按「不可取消」表达 throw new OutboundCancelBlockedException(WarehouseException.builder() .message("hengjian refused cancellation: " + e.getMessage()) .operation(OP_ORDER_CANCEL) .warehouseCode(ctx.warehouseCode()) .provider(provider().name()) .requestId(ctx.requestId()) .platformCode(e.platformCode()) .rawResponse(e.rawResponse()) .retryable(false)); } return CancelResult.builder() .outboundRequestNo(orderNo) .providerOrderId(String.valueOf(orderId)) .eligibility(CancelEligibility.FREE) .cancelled(true) .rawStatus(json.stringAt(raw, "message")) .build(); } /** * 按单号或订单 id 查一行,用于补全取消需要的另一个键。 * *只认精确匹配:列表接口的 {@code orderNos} / {@code orderIds} 过滤是否精确 * 文档没说,取回来再逐条比对,避免拿近似结果去取消别的单。
*/ private HengjianOrderListDtos.OrderRow findRow(WarehouseContext ctx, String orderNo, Long orderId) { Map恒健没有独立的包裹接口,发货信息就在详情报文里。按 {@code trackingNo} 去重 * (同一包裹可能同时以「实际包裹」和「面单信息」两行出现),实际包裹 * ({@code packageFlag=0})优先。
*/ @Override public List恒健收的是 UTC 日期({@code yyyy-MM-dd}),不是时间戳;跨度不超过 * {@link HengjianConstants#ORDER_LIST_MAX_DAYS} 天。用「起止都含当天」的口径, * 所以计算跨度时把 end 当天算进去。
*/ private void addDateRange(WarehouseContext ctx, Map上限 100 是文档明写的(「一页的行数,默认最高 100」)。超过时 * 显式拒绝而不是静默截断:调用方按自己传的 pageSize 判末页, * 被悄悄改小会误判「还有下一页」。
*/ private int requireRows(WarehouseContext ctx, int pageSize) { if (pageSize <= 0) { return HengjianConstants.ORDER_LIST_MAX_ROWS; } if (pageSize > HengjianConstants.ORDER_LIST_MAX_ROWS) { throw validation(ctx, OP_ORDER_QUERY, "hengjian order list rows must not exceed " + HengjianConstants.ORDER_LIST_MAX_ROWS + ", got " + pageSize); } return pageSize; } /** 逗号拼接(恒健多条单号用逗号分隔)。 */ private static String joinIds(List恒健的面单就是 {@code attachInfoItems} 里的一条附件;声明了 * {@code PLATFORM_LABEL_DELIVERY} 却不给文件,仓没有面单可打,等于静默失败。
*/ private static void requirePlatformLabelSupported(OutboundCommand cmd) { if (cmd.labelMode() == LabelMode.PLATFORM_LABEL && (cmd.labelContentBase64() == null || cmd.labelContentBase64().trim().isEmpty())) { throw new IllegalArgumentException( "labelContentBase64 is required when labelMode=PLATFORM_LABEL for " + cmd.outboundRequestNo()); } } /** 原始响应可能含 PII,异常里只留短片段。 */ private static String safeRelay(String raw) { if (raw == null) { return null; } return raw.length() <= 300 ? raw : raw.substring(0, 300) + "..."; } // ------------------------------------------------------------------ 商品 /** * 创建 / 编辑商品({@code POST /v1/product/save})。 * *接口是保存语义:同一 SKU 再调即更新,所以不区分 create 与 update, * 也不像信仓那样先查一次再决定调哪个接口。
* *响应只有 {@code code / message},没有 data,因此结果里的 * {@code status} 固定为 {@code SAVED}、{@code rawStatus} 取仓方的 message—— * 仓方并不告诉我们这次是新建还是更新,不能替它编。
* * @throws IllegalArgumentException 恒健要求但统一模型未给的非空字段缺失(本地拒绝) */ @Override public ProductResult createOrUpdate(WarehouseContext ctx, WarehouseProduct product) { HengjianProductSaveDtos.SaveProductRequest body = HengjianProductMapper.toRequest(product); String raw = execute(ctx, HengjianConstants.PATH_PRODUCT_SAVE, body, OP_PRODUCT_SAVE); return ProductResult.of(body.sku, SAVED, json.stringAt(raw, "message")); } /** * 分页查商品({@code POST /v2/product/queryPage})。只读,不走幂等。 * *请求的 {@code pageSize} / {@code pageNum} 文档标 STRING; * 文档的字段说明把两者写反了,按响应里的含义实现 * (pageSize = 每页条数,pageNum = 页码)。
* *响应 {@code data} 是分页对象(不是数组);{@code total} 用来判断是否还有下一页。
*/ @Override public Page返回的 {@code warehouseCode} 可直接用于下单、库存查询等接口。
*/ @Override public List返回物流产品代码(如 {@code UPS2DAM_HL}),可直接作为下单的 {@code carrierCode}。 * 按出现顺序去重。
*/ @Override public List恒健这个接口没有仓维度,拿到的是组织级清单;{@code warehouseCode} * 仅用于写进结果字段,便于调用方区分来源。需要「某仓支持哪些渠道」用 * {@link #productsOfWarehouse}。
*/ @Override public List返回形状与 {@link #products} 不同:{@code data} 是以仓代码为键的对象, * 不是数组;只取请求的那个仓,混进别的仓的渠道会让「仓不支持该渠道」 * 变成仓方报错。
*/ public List