nexxus / nsk Goto Github PK

Een product moet ook een status krijgen. Nu heeft alleen een order een status.

NB: Het wordt van belang dat deze niet verward worden. Als de gebruiker de neiging krijgt om iets betreffende een bestelling op te slaan als productstatus, dan moet bij hem/haar een alarmpje afgaan/

Customer/Partner entiteiten moeten voldoen aan UML, dus deels herschrijven

Functionality:

• Able to bind products to attributes. For example a hard drive that got added to a Laptop should have it's SKU linked to it via an attribute.

Functionality:

• Upload and save images to products
• Bind an existing image to a product, especially handy for product groups

Currently products are made with a Create form, eventually this will be done with a flexible order form where every product is bound to an order.

Terminology is viewed from a company's perspective: Purchase form is for things that the company purchases, sales is for what the company sells.

With payment modules like Ideal Omnikassa 2.0

Form entries will automatically be scheduled for route, volume and weight
http://www.copiatek.nl/ophaaldienst/

Functionality:

• Retrieve attributes from Tweakers API to add to products

For example, C0000 for computers, L0000 for laptops

so if you repair a bike or computer, you need to be able to add parts that were used to do the actual repair. This is a must have for anwb to work with (particularly in the app)

Parts & Supplies still belong to certain categories but are probably only visible in distinct locations.
Some parts are only suited for specific procucts.
Not every wheel will fit into any bike...
Not every ssd drive will fit into any laptop

• Retrieve Microsoft keys based on the windows/Office COA, API may or may not exist

Functionality:

• Bind tasks that have been fulfilled to attributes of other products

Dropdowns that could potentially become very big should have some sort of search feature that allows them to type the name of the entity they want to receive.

Functionality:

• Able to upload files to a product via the edit form. Primarily for Wipe reports, Windows certificates, etc.

The need for automatic mapping and routing for the cars to pick up and make deliveries

The T&T page will be split into two pages.

• View stock
  -- The index will return a view of the current stock. This is determined by subtracting the Sale orders from the Purchase orders and showing what's left.
• View Product List
  -- This shows the possible products that can be added to orders. This will retain most of the functionality from the old page.

Probably a dropdown bug, should be fixed by putting USER as default value

Coolblue has a great system actually.
When a product is sold, it will likely be handed-out personally. In that case someone should add a signature for confirmation of receiving goods (tablet/smartphone).
In case of ANWB someone will transport bikes between locations. It must be possible to administer this easily through the app.

This will be fixed by moving all of the twig files back to the App folder.

Currently only possible to create users via the command line, or via external form (automatically logs out admin)

Functionality:

• Able to fill in product attributes with dropdowns. This needs to work together in some way with open input fields, perhaps a dynamic dropdown that suggests options as you type (options obtained from a table?)

• Checkbox for filling in existing barcode, if new product don't show input field
• Disable enter presses in the field itself

To work with other systems such as Nationale Nederlanden

The T&T page will be split into two pages.

• View stock
  -- The index will return a view of the current stock. This is determined by subtracting the Sale orders from the Purchase orders and showing what's left.
• View Product List
  -- This shows the possible products that can be added to orders. This will retain most of the functionality from the old page.

https://www.avery.com/

Currently products are made with a Create form, eventually this will be done with a flexible order form where every product is bound to an order.

Terminology is viewed from a company's perspective: Purchase form is for things that the company purchases, sales is for what the company sells.

• Purchase form: Choose between creating a group of multiple products or making a product with a quantity

Or as a module to enhance Exact Online (Unit4 etc) This way Exact Online can be used as a distributor