Overview
Understanding J.Press integration
Who this is for: Factories, mills, trim and packaging suppliers, and the fulfillment provider that ships e-commerce orders for J.Press, and the teams that run their orders and shipments. Carriers send their own status messages and are a separate relationship.
Scope: Vendor, fulfillment-provider and carrier exchanges are different relationships; confirm which applies to you.
J.Press is an Ivy-style menswear brand with stores in the US and Japan. It sells direct to consumers through its own stores and website. ECOM's directory lists it under Traditional menswear.
J.Press is an Ivy-style menswear brand with stores in Washington, New Haven and New York and an online store (its own site), and the brand is reported to be part of Onward Group. Three relationships appear on this page: vendors that supply product (850, 855, 856, 810), the fulfillment provider that receives warehouse orders and confirms shipment (940, 945) and carriers (214 status). The table is written from a vendor's side: warehouse orders (940) and shipment confirmations (945) are exchanged with the party that runs J.Press's fulfillment. If you are that fulfillment provider, the 940 and 945 directions are reversed for you.
Operations in two countries mean different supply chains and license arrangements for each market. As a retailer, J.Press buys from vendors and factories that usually follow a vendor or routing guide covering purchase orders, ship notices, carton labels, delivery windows and invoicing, and vendors should expect penalties when those rules are missed.
J.Press's own EDI or API specification is not part of this guide. What follows is typical practice for traditional menswear, so confirm the documents, X12 version, delivery method and testing steps with J.Press's trading-partner team. ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications, as software, as a managed service or both.