Billing
9 months ago

Billing API Update (11.04.2024)

New Features
  • We have added a new section to the Billing API called warehouse actions. You can add default Warehouse Actions such as Unload 40ft container, put away pallet etc and you can set a default price too. If you want to charge a customer a price that is non standard you can easily change their pricing for some or all of the default actions in the new GUI. Creating a warehouse action is as easy as clicking the "Create Charge" button and then choosing the account type and entering a quantity and reference. The charge will be immediately added to the customers next billing cycle. 
Billing
10 months ago

Billing API Update (03.04.2024)

New Features
  • Add fixed pricing for a specific SKU in picking rates. This feature allows you to choose an additional fee for a SKU or a set fee i.e. if you have the SKU LEAFLET1 you can choose to add 10p or you can choose to SET 10p. This function also allows a negative value so you can ask the system to deduct from the picking rates also.
  • Allow the ability to charge by cubic as well as storage locations. This feature allows you to bill storage as cubic units or by the current way of telling us what location types and quantities you want bill for. The cubic storage is decided by setting cubic bands i.e. up to 5, up to 10, up to 20 and then deciding a price per cube if the total cube falls in that band. Although the system GUI shows CBM for cubic metres the calculations are unitless and you should submit in the units you want to work in. It would be typical for you to send the call with the dimensions in metres.
These new API calls have not been added to the WMS yet but are scheduled to be soon.

The call for cubic storage is a POST request to https://production.billingapi.co.uk/api/submit-cubic-storage-charges with the headers of Bearer Token in the format of Bearer <<insert billing api token from billing api home page>>.

{
    "customer_dc_id": "Insert customer id",
    "items": [
        {
            "sku":"SKU1",
            "height":"1",
            "width":"1",
            "length":"5",
            "quantity":"3"
        },
        {
            "sku":"SKU2",
            "height":"1",
            "width":"1",
            "length":"1",
            "quantity":"11"
        }
    ]
}

The call for recurring storage charges is to https://billing.courierapi.co.uk/api/update-recurring-storage-charge-quantities and looks like the below where type_id is the locations storage type as defined in the billing api GUI.

[
    {
        "type_id": 2,
        "dc_customer_id": "SAND-01",
        "quantity": 3
    },
    {
        "type_id": 3,
        "dc_customer_id": "SAND-01",
        "quantity": 44
    },
    {
        "type_id": 4,
        "dc_customer_id": "SAND-01",
        "quantity": 33
    },
    {
        "type_id": 5,
        "dc_customer_id": "SAND-01",
        "quantity": 12
    }
]
Billing
12 months ago

Billing Update (06.02.2024)

Added the ability to delete an API user from Billing API using the below call

DEL to https://production.billingapi.co.uk/api/customer/<<customer dc_id>>

You will need your Bearer token from within the GUI and content type is application/json
Billing
12 months ago

Billing Update (30.01.2024)

New Features

1. We have released the ability in Billing API to set a minimum quantity for recurring charge rules. This is particularly useful for storage charges where a customer needs to be billed for a minimum number of pallet spaces regardless of how many pallet spaces currently have a SKU in the location. 

2. We have added a GET Quote call to Billing API to allow a customer to make an API call and get access to a list of services and pricing from Billing API for a particular data set. The body is the same as a create label call and the URL to access the call is https://production.billingapi.co.uk/api/customer-routes/get-quote.
You will require 3 headers to make the call work which are:
client_name : the name of the business in Billing API
customer_dc_id: the dc id of the customer from the customer record
customer_key: a new field contained in the customer record

An example of the response you could expect is below

[
    {
        "service_code": "YODEL-2VSN",
        "service_name": "Yodel Xpect Mini 48",
        "courier": "Yodel",
        "price": {
            "shipping": [
                3
            ],
            "surcharges": [
                0
            ],
            "picking": 0,
            "parcel_rules": [
                []
            ],
            "packaging_charges": [],
            "total": 3
        }
    },
    {
        "service_code": "DPD-12",
        "service_name": "DPD Next Day",
        "courier": "DPD",
        "price": {
            "shipping": [
                5
            ],
            "surcharges": [
                0
            ],
            "picking": 0,
            "parcel_rules": [
                []
            ],
            "packaging_charges": [],
            "total": 5
        }
    }
]
Billing
12 months ago

Billing API Update (22.01.2024)

1. New Features:

  • Added the ability to specify default packaging types and prices for all customers instead of adding one at a time. 
  • Added the ability to add custom packaging types per customer
  • Added a new GUI for increasing base prices across whole portfolio of pricing 

Powered by FeedBear