Parked Feature List

Packing	Size set packaging	In Fashion B2B Outwards, for orders going to stores, store teams want to have styles packed in a "size-set" packing, meaning all sizes for a style should be packed together.	This does not add additional value to our product. This is a minor optimization which added more complexity in the operations than it solves	This can easily be handled on OPS Level
Masters	"X" Number of Custom Fields to be added in Article Master	Clients want to store 'X' number of attributes in WMS's article masters and use it with reporting for their analytics	This does not add additional value to our product	This information should ideally be stored in ERP or PIM
Picking	Picking by clients wise in Single WMS	3PL Customers who are running operations for multiple clients want to have separate picking for each client	This is will reduce picking efficiency.	Ideally, after packing, a AWB based sorting is present that should be used to sort packets for different clients
Orders	Backorders	WMS should be able to take backorders and later convert a list of backorders to a PO. Applicable to Myntra JIT kind of channel models	This does not add any additional value to our product.
Packing	Packagining Inventory management & Packaging suggestions based on product dimension	Keeping tracking of how much packing material is present in the system, how much is getting consumed with orders, and what package SKUs are there. Also, suggest what package sku to be used in order	This does not add any additional value to our product.
Packing	E-invoicing - direct integration with government portal	Direct integration with Govt portal	It is always recommended to use E invoice services through one of the GSP partners.	We are integrated with clearTax as our GSP partner for E invoicing More details here - https://cleartax.in/s/gst-suvidha-provider-gsp-e-invoicing-api-access
Orders	QC reason wise Inventory & allocation in Orders	Place orders for QC fail inventory for a specific reason. i.e While placing the order client wants to define that all 'stitch damage' items should get allocated to this order	This is impossible for us to perform from an architectural standpoint.	WMS has a features where user can upload a List of Item-ids to be picked for an Order. This can be used to solve the use case
Orders	Auto cancellation of items in the Last piece lost Orders	Auto cancellation of items in the Last piece lost Orders	This does not add any additional value to our product. This is a very minor optimization for a very edge case scenario	Option in UI to cancel order and sku wise qty CSV upload to cancel orders and line items.
Integration	Direct Integration with XYZ logistics provider	Integrate with X , Y, Z logistics partner, build intelligence to select partner dynamically during packing etc	Any customer will need integrations with multiple logistics partners. And then the customers will need mechanism to select the required partner. There are already companies doing this. Logistics aggregators like Clickpost and Shiprocket exist for these various purposes. They have all the intelligence built around when to select what partner, customisable as per business rules etc. So as a Company it does not make sense for us to build the same logic again.	We have already integrated with Logistics aggregators. Clickpost, shiprocket. We are open to integrating with more logistics integrators if required. Clients should use logistics integrator services to remove dependency on any single logistics provider.
Orders	Handling Packs and set.	Handling size ratio sets and size sets	We are supporting UOMs. But we wont be able to supports sets and packs due to architectural constraints	make different pack skus and eaches sku. and treat them differently
Warehouse operations	Bulk Operations via RFID tags	Bulk operations via RFID means RFID device is able to read multiple RFID tags and perform operation for them. for example GRN or Cycle count	This is impossible for us to perform from an architectural standpoint.	-