Looking for the questions? Webinar 2.7 Test Questions
- Charge for each different SKU (different product) added to the order. For example, picking 100 boxes of one product would normally be faster than picking 1 box each of 100 products, so the SKU charge is implemented to cater for this.
The SKU charge is counted as the number of different products added to the order.
Number of Unique Products x Outbound SKU Charge = SKU Charges
See: Customer Charges Fields & Descriptions
- No, picking charges should not be run through Adhoc Charges as Adhoc Charges are for charges which are applied on an ad-hoc basis, but cannot be automated. Instead, Picking Charges should be configured for the various units of measure that are picked for the customer. See: Warehouse Handling Fees and Stock Selection #HowtosetupHandlingCharges
- Within the Customer Charge, set the "Picking Charge Option" to "Intelligently Charge Pallet Picks Where Possible". More info available here: Warehouse Handling Fees and Stock Selection, then load in $2.50 pallet picking charges to the customers charge card.
- The picking fees would be automated through the Warehouse Handling Fees listed above. The Fork-load fee however would be charged through the Consignment. You would have a Delivery Run called "Pickup from Warehouse" which would be linked to a Rate Zone of "Pickup", then use pallet rates within the transport charging.
- Non-cumulative, as you want to bill all picks at the same rate ($0.35). Refer to: Sliding Scale Rates Configure the "Picking Charge Option" to be: "Charge Base Unit of Measures".
- If an invoice is deleted, the jobs on that Invoice simply go back to being un-invoiced, and will reappear on the next invoice that is created. This prevents CartonCloud clients from ever having jobs disappear from invoicing.
- Following on from the previous question, as every job created in CartonCloud "must be" invoiced, test jobs will keep attaching themselves to invoices if they're removed. To prevent this, you need to create an invoice for all the test jobs, add them, and then void the invoice. This way the jobs are treated as "Invoiced", and the invoice itself is Void.
- Leeching Invoices are invoices which pull in billable jobs each day so admin staff can resolve Charge Errors throughout the week, rather than all of them on the invoicing day. See: Leeching Invoices The job needs to have "Finalise Charges" enabled, otherwise it will create a Charge Error when it goes to invoicing as the system won't know how to handle the manually added charge.
- Create two product types, one called "Inside" and another called "Outside". Then configure the Inside Locations to be of type "Inside", but able to store products of type "Ambient". Do the same for the Outside locations.
Using the "Charge Product Type Option" within the "Customer Charge", set the field to "Warehouse Location" so it bills based on the Product Type of the Warehouse Location (Inside / Outside) rather than the Product type of the product (Ambient).
- New storage charges will be applied even if the location was charged for existing storage. This means that if a location was in use at the start of the storage period, and then new stock arrived and went into the same location, it'll be charged again as 'New Storage'. This also applies if the location was in use at the beginning of the storage period, then went empty (stock went out), and then more stock was put into the location. By enabling 'Double Charge Storage', you'll charge the location once for the existing product, and again for the new stock coming in.
- "Max Number of New Charges Per Location" controls how many times in a given storage period the same location can be billed for new stock coming in. If you had a single location in which 3 different pallets came in and went out, you may not want to charge the client for 3 pallets of storage. You can limit how many times a location is charged through this field, entering 1 for example would limit you to only charging new storage once within the storage period.Delivery Zones link Postcodes and Suburbs to Delivery Runs and Rate Zones. As Consignments contain addresses which have postcodes / suburbs, the postcode and suburb are looked up in the Delivery Zones list in order to work out which Delivery Run to allocate too, and also which Rate Zone to price using.
- Export / Import Delivery Zones to get them done in bulk.
- No you can just use a single Rate Zone called "Metro", then simply load individual Customer Charges against the same Rate Zone, so "Metro" is charged differently depending on the customer.
- Create a "customer-specific" Delivery Zone for that particular suburb / postcode which links to the Outer Rate Zone.
- Create a Delivery Run called "Pickup" which is linked directly to the Rate Zone "No Charges". Then for all consignments being picked up, allocate to the "Pickup" Delivery Run - this will then charge nothing. You can also have these jobs appear on a tablet or phone for signature capture in the warehouse automatically without needing to perform driver allocation via: Automatically allocate Consignments to Drivers from Delivery Runs
- An A2RZ should be used when a particular address needs to be charged differently to the Suburb / Postcode it sits within, so rather than charging based on the Suburb / Postcode, charge based on a manually selected Rate Zone for the Address. More Info: Address to Rate Zone Mapping
- No, applying a Rate Zone directly to a Consignment is the most specific you can get, and therefore overrides everything else. Refer: How Transport Rates are Calculated
- Within the transport rate card, in the Spaces section set it to "Ignore (No Charge)"
- Edit the Customer Charges, Set the "Fuel Levy Offset" to 10%, and change "Ignore Base Setting" to "Yes"
Adhoc ChargesWithin each Customer Charge you can override the default Adhoc Charge pricing. Therefore, for each of the customers who need to be charged at a different rate for Pallet Rework, you can simply adjust the rates within their Customer Charge card. If they're using a common Customer Charge shared by other clients who should not be charged at the special rate, the Customer Charge will need to be duplicated. This process was covered in Webinar 2.5