Continuing the discussion from Bulk import of product:
There is a lot of discussion on this thread. I have now started the process of capturing our current collective thinking in a document… boldly titled Data Import SRS (software requirements specification).
- Use case
Still to do:
- User Interface Mocks
@MyriamBoure @oeoeaio @Kirsten @nick @CynthiaReynolds @sreeharsha @Oliver @sstead @tschumilas @danielle
Please take a look, comment and suggest changes! Would be great to continue getting your input this specification.
Create: as an enterprise, I have all my existing products in a spreadsheet. It would be much easier to get started by formatting and uploading my spreadsheet than creating each individually
- assume i am happy to come back and add images later
- create relevant ‘properties’ first
- assume the producer profiles are created, with E2Es ready
Update Prices: As a wholesaler, I have many products and the prices change regularly. It is much easier to make these changes in a spreadsheet and import them all at once
- may include products from multiple producers
- my price changes may need to be picked up by others
[NB: this may not be the actual wholesaler but another user managing on their behalf]
Update Inventory: As an Enterprise, the availability of my products changes week to week, I want to be able to upload CSV and have p/v that aren’t included removed from my inventory
- my changes to product availability may need to be shared with other enterprises
Potential Buying Group integration (SS) As a buying group, I can receive an availability report from my supplying hub, make some modifications (to pack sizes, price etc), and then upload this into my inventory.
- This feature may not be needed if a more ‘built in’ buying group solution is provided.
- This is analogous to the current LettuceShare process used by buying groups
- As a starting point, these products may not be linked to the actual producer profiles, instead allocated as dummy products to the buying group.
Issues / Questions:
- are we uploading into p/v values; those in inventory lists or both? depends on separation of products / inventory
- if we separate p/v and inventory, then the initial ‘profile / product info’ and later ‘inventory info’ may need to be imported separately?
- working mostly with inventory lists would mean that p/v not included in the csv could simply be set to hidden (no need to delete or change values)
- will need processes for dealing with
- invalid data
- non-existent producers