Access to add and change pages is restricted. See: https://cwiki.apache.org/confluence/display/OFBIZ/Wiki+access

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Since last more than a decade now, OFBiz has been helping us in building eCommerce stores and using its OMS + Fulfillment abilities for servicing retail businesses. Time has changed with the growing customer expectations new systems have emerged for serving different functions e.g. in any established brand there will be designated systems to do certain jobs such as PIM(Product Information Management), E-commerce, POS(Point of Sale), OMS(Order Management System), Customer Service, WMS(Warehouse Management System), ERP(Accounting System), etc. 

If it's a fresh start for a brand and no legacy systems are there, OFBiz as PIM, eCommerce(API mode), OMS, WMS can be the choice, which can surely serve the business and scale up when needed without any additional development or maintenance effort. 

As mentioned earlier, at the next level, we find an established brand where the business is tied up to operate with legacy platforms. There are various reasons for this limitation of not being able to completely replace a stack of applications with OFBiz in one go. In this case, if the business considers OFBiz as OMS, then in most cases, the challenge is to efficiently and cost-effectively integrate with PIM + Sales Channels(eCommerce and POS) + Legacy WMS + ERP systems. 

This document presents expected capabilities from OFBiz when used as OMS in an ecosystem and integration challenges with legacy systems.

Here are the functional expectations:

  1. Real-time inventory visibility
  2. Order routing to the appropriate facility for fulfillment based on a defined strategy by the business
  3. Order splitting for faster fulfillment of available items on the order
  4. Fulfillment application to be used at Stores(BOSS - Buy Online Ship-to-Store)for picking, packing, and shipping Label 
  5. Store inventory management
  6. Ease of managing most popular customer journeys across the channels like BOPIS(Buy Online and Pick in Store), BORIS(Buy Online Return in Store), and Endless Aisle.
  7. Preorder and Backorder Management

Integration expectations:

  1. Secure
  2. APIs availability(Headless)
  3. Data import and export functions(CSV)
  4. Middleware support for information exchange in different formats expected by source and the destination
  5. Easy and cost-effective system maintenance 

Some of the above-mentioned expectations are already supported by OFBiz at the service level. An audit will help us identify a roadmap to work on. The latest example of this is one initiative in the community from Arpit Mor on this thread. 






  • No labels