New Product: Difference between revisions
No edit summary |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
=== Ask the Team === | |||
- Which computer for production? | |||
- Which computer for shipping? | |||
- Which existing production process is the new product most like? | |||
- Product dimensions? | |||
- Product weight? | |||
- Packaging - new or existing? If new what is size, weight, and branding? | |||
=== Database === | |||
- Add to product_category table | |||
- Add to prod_group table. Need estimate of ratio of product cost to customs value for ship_mult value. | - Add to prod_group table. Need estimate of ratio of product cost to customs value for ship_mult value. | ||
| Line 4: | Line 23: | ||
- Add to provider_product table (if provider using skus or order item specs not already found in product_info) | - Add to provider_product table (if provider using skus or order item specs not already found in product_info) | ||
- Add | - Add packaging (all packaging for different order sizes) | ||
Dimension, weight | |||
packaging table (if using new branded packaging or packaging not already on file) | packaging table (if using new branded packaging or packaging not already on file) | ||
| Line 21: | Line 40: | ||
- Set up routing to routing and/or spec_routing tables | - Set up routing to routing and/or spec_routing tables | ||
- Add to | - Add product group to access table if departmental access code is used | ||
- Set up daily reporting as requested or according to similar products | |||
=== Workstations === | |||
- Choose a production workstation and install production software (if not already installed) | |||
- | - Choose a ship workstation and add product group to /Fulfiller/scripts/config.json | ||
Production development notes | === Production development notes === | ||
- If code is added or excluded based on provider this should be done instead through configuration options in assembly.json rather than via provider checks in production code. | - If code is added or excluded based on provider this should be done instead through configuration options in assembly.json rather than via provider checks in production code. | ||
Latest revision as of 10:38, 15 September 2026
Ask the Team[edit]
- Which computer for production?
- Which computer for shipping?
- Which existing production process is the new product most like?
- Product dimensions?
- Product weight?
- Packaging - new or existing? If new what is size, weight, and branding?
Database[edit]
- Add to product_category table
- Add to prod_group table. Need estimate of ratio of product cost to customs value for ship_mult value.
- Add to provider_product table (if provider using skus or order item specs not already found in product_info)
- Add packaging (all packaging for different order sizes)
Dimension, weight
packaging table (if using new branded packaging or packaging not already on file) packaging_product table (to map new product to packaging) provider_packaging table (if provider has reportable packaging skus)
- Add records to product_info for all variants
Product price to provider Variant weight Dimensions (only if using size to determine packaging) Ship description (if different from its product group)
- Set up routing to routing and/or spec_routing tables
- Add product group to access table if departmental access code is used
- Set up daily reporting as requested or according to similar products
Workstations[edit]
- Choose a production workstation and install production software (if not already installed)
- Choose a ship workstation and add product group to /Fulfiller/scripts/config.json
Production development notes[edit]
- If code is added or excluded based on provider this should be done instead through configuration options in assembly.json rather than via provider checks in production code.