Hi Krzysztof Ćwirko, Most of the items you asked for available with framework. Also OFBiz is enough flexible to integrate with any UX technology and can communicate with any other system as all the business api's in OFBiz can be exported for outer world. I'll share more details on each line item soon. You can go thru the following details to map your requirements with features offered by OFBiz.
- https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Features - https://cwiki.apache.org/confluence/display/OFBIZ/Business+Process+Reference+Book Rishi Solanki Sr Manager, Enterprise Software Development HotWax Systems Pvt. Ltd. Direct: +91-9893287847 http://www.hotwaxsystems.com www.hotwax.co On Fri, Sep 15, 2017 at 3:56 PM, Deepak Dixit < deepak.di...@hotwaxsystems.com> wrote: > HI Krzysztof Ćwirko, > > Your email has been moderated, Please subscribe to user mailing list > http://ofbiz.apache.org/mailing-lists.html > > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > www.hotwax.co > > ---------- Forwarded message ---------- > From: "Krzysztof Ćwirko" <kcwi...@bluesoft.net.pl> > To: user@ofbiz.apache.org > Cc: > Bcc: > Date: Fri, 15 Sep 2017 12:06:55 +0200 (CEST) > Subject: Apache OfBiz solution - requirements > > Hello, > > I`m business analyst in IT company and we are considering to present your > system solution to our logistic client but first we need to make sure > whether your product meets the following functional requirements: > UX seller - compatible with RWD (Responsive Web Design) to be embedded in > the mobile application sellers used to sell goods at the market hall in the > market > UX Service partner - enabling collaboration with local couriers without IT > systems (work on client`s logistic system) > UX client`s employees that enables (depending on permissions) all > operations available on the platform and its configuration / > parameterization > Arrange the delivery date by marketers when selling goods to the customer, > taking into account all forms of delivery (including local transport) > Forwarding customer`s delivery orders to the central warehouse system > Change supplier and delivery dates > Transmission of information on delivery costs, possible deadlines for the > cart > Ordering / delivery of couriers for deliveries: market - client > Shipment status monitoring > System configuration for: basic platform`s parameters, prices, transmission > capacity, etc. > Alert in case of problems / errors of KPIs exceeding individual process > steps > Logistics processes for the sale of goods on request > Support for drop shippment processes > Integration of warehouse availability information, support for inventory > synchronization between the customer's Warehouse Management System (WMS) > and central warehouse system > Support for pre-allocated cross docking (PAXD) - consolidation of > deliveries. > Support for centralized purchase of goods on behalf of rmarkets (BBXD - > purchase order consolidation) > Data transfer to BI system – data feed in 1h interval > Integration with couriers > Integration with central warehouse supplier: > a) within the scope of the carried out transports > b) in terms of orders from suppliers > c) in terms of order synchronization, order status > d) in the field of consignments notification > e) in terms of delivery tools (unloading window-point) > Integration with e-commerce or other online / offline sales systems: > a) in the field of operation - online integration offering, inter alia: > 1. {SupplyAbility} Opportunity (cart) > 2. {Delivery} DeliverySimulation (basket, selected delivery option) > 3. {SupplyAbility} PossibleChangeDate (order) > 4. {Supply} saveDelivery (cart, Delivery) > b) in the scope of synchronization master data eg product, shop, etc. > Integration with WWS - GMS (General Management System) class: > a) for monitoring customer orders (central warehouse and stores) - active > active polling via the API Management integration layer > b) regarding the control over the possibility of delivery to the customer > from the inventory of central warehouse: correct sales document, paid > product > c) for state synchronization between Central Warehouse and WWS - EDIFACT > message translation > Basic data configuration > a) Couriers, their activities and other parameters > b) Mapping status between couriers, central warehouse, customer systems, > etc. > Operational reporting > Great integration flexibility - preferred use of API management such as > WSO2 API > Support for Oauth 2.0 protocols > Open Opportunities for Platform Development Client - Transfer of code > ownership or non-exclusive license to modifications > Proposed implementation based on microservices in container environment > > I would like to kindly ask you to send response with short comment for each > position of requirements list. > > Best regards, > > -- > *Krzysztof Ćwirko* > Business Analyst > tel. +48 503-099-939 > > BlueSoft Sp. z o.o. > Aleje Jerozolimskie 96 > 00-807 Warszawa >
