Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »


  1. What does "Outbound SKU Charge" do and when should it be used?
  2. If a client is charged $0.40 per carton picked, should this be handled through Adhoc Charges?
  3. Assuming you have two products on one location which total 10 cartons, and you typically charge $0.40 per carton unless the whole pallet can be picked because you're taking everything from that one pallet (in which case you would charge a $2.50 pallet pick charge), how would you automate this?
  4. Assuming you charge picking fees for an order of $0.40 per carton, and then wish to charge a fork-load fee for lifting the pallet into a pickup vehicle (assuming the client is picking up from the warehouse), how would you automate this?
  5. Would you use a cumulative or non-cumulative sliding scale to charge picking rates whereby 10 cartons or less are charged at $0.40 per carton, and if there are 11 or more cartons all cartons are charged at $0.35?
  6. Assuming a product has 6 units per carton, and you often pick in cartons but always want to charge for the units picked, how would this be configured? 

  7. If an invoice is deleted, what happens to all the jobs (Sale Orders, Purchase Orders, Consignments etc) that were on the Invoice?
  8. If your CartonCloud account contains a bunch of test jobs, how do you prevent them from being invoiced?
  9. What are leeching invoices?
  10. If a job is being manually charged, what other step is required to ensure it doesn't create a Charge Error?

    Adhoc Charges
  11. Assume you've created an Adhoc Charge called "Pallet Rework", which is a charge for restacking pallets on putaway, but want to vary the price of this across a handful of customers, how could this be achieved so it is automated going forward?

  12. Assuming a warehouse has two types of locations, "Inside" and "Outside", whereby both are ambient, and ambient stock can be stored in either but the Inside locations are charged at $3.50/week whereas the Outside locations are charged at $2.00/week, how could this be configured to be automated?
  13. What does "Double Charge Storage" do?
  14. What does "Max Number of New Charges Per Location" do?


  1. 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
  2. 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
  3. 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.
  4. 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.
  5. Non-cumulative, as you want to bill all picks at the same rate ($0.35). Refer to: Sliding Scale Rates
  6. Configure the "Picking Charge Option" to be: "Charge Base Unit of Measures".

  7. 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.
  8. 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.
  9. 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
  10. 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.

    Adhoc Charges
  11. Within 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

  12. 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).
  13. 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.
  14. "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.

Webinar 2.6 Test Answers

  • No labels