You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--README.md
Added section to detail the Sender Delivery Notice To Customer API Endpoint and provide a coding example.
--APIv1Constants.php
Added constanst containing the name of API endpoint for an org to send a delivery notice
--APIv1EndpointOrgSendDeliveryNoticeToCustomer.php
Created class to handle calling the Squizz API for sending a delivery notice to a customer in the Squizz platform.
--APIv1EndpointRunnerRetreiveOrgESDDataProducts.php
Fixed coding example for retrieving product data from another organisation to retrieve product data, instead of make model mapping data which was incorrectly copied into this file when previously committed.
--APIv1EndpointRunnerSendDeliveryNoticeToCustomer.php
Created class to show an example of how to call the SQUIZZ API endpoint for an organisation to send a delivery notice to a customer.
* [Import Organisation Data Endpoint](#import-organisation-data-endpoint)
33
34
* [Import Organisation Sales Order Endpoint](#import-organisation-sales-order-endpoint)
@@ -1861,6 +1862,162 @@ See the example below on how the call the Send Customer Invoice To Customer endp
1861
1862
?>
1862
1863
```
1863
1864
1865
+
### Send Delivery Notice to Customer Endpoint
1866
+
1867
+
The SQUIZZ.com platform's API has an endpoint that allows an orgnisation to send delivery notices (also known as shipping notices, freight notices, advanced shipping notices) for goods it having delivered to a customer, notifying where the ordered goods are being handled in the dispatch and delivery/shipping process.
1868
+
This endpoint allows a supplier organisation to automate the sending out of delivery notices to its customers, allowing either individuals ordering in squizz to receive these notices, as well as allow customer organisations to automate the receiving of delivery notices and importing them back into their own systems.
1869
+
Many delivery notices may be sent for the same delivery of ordered goods, containing a status and message outlining where the goods are currently located. This can allow customers to receive many notifications as it progresses. It's up to you to determine how often the customer should be aware of delivery progression.
1870
+
- The endpoint relies upon a supplier organisations first importing customer accounts within the SQUIZZ.com platform that the delivery notices are associated to.
1871
+
- If the delivery notices needs to be forwarded onto customer organisations, then endpoint either relies upon a connection first being setup between the supplier and customer organisations within the SQUIZZ.com platform, or the supplying organisation setting up a data adaptor to export the customer delivery notices to the customers external system. The first option is preferred since the supplying org then doesn't need to know what system the customer organisation is running.
1872
+
- The endpoint has a number of other requirements. See the endpoint documentation for more details on these requirements.
1873
+
1874
+
Each delivery notice needs to be imported within a "Ecommerce Standards Document" that contains a record for each delivery notice. Use the Ecommerce Standards library to easily create these documents and records.
1875
+
It is recommended to only import one delivery notice at a time, since if an array of delivery notice is imported and one notice failed to import, then no other notices in the list will be attempted to import.
1876
+
Read [https://www.squizz.com/docs/squizz/Platform-API.html#section1550](https://www.squizz.com/docs/squizz/Platform-API.html#section1550) for more documentation about the endpoint and its requirements.
1877
+
See the example below on how the call the Send Delivery Notice To Customer endpoint. Note that a session must first be created in the API before calling the endpoint.
The SQUIZZ.com platform's API has an endpoint that allows organisation notifications to be created in the platform. allowing people assigned to an organisation's notification category to receive a notification.
1866
2023
This can be used to advise such people of events happening external to the platform, such as sales, enquires, tasks completed through websites and other software.
* This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
5
+
* This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
6
+
* You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.
* Class handles calling the SQUIZZ.com API endpoint to send one more of an organisation's delivery notices to the platform, where they are then sent to a customer person, or organisation (optionally for importing and processing)
23
+
* This endpoint allows the notifications of ordered goods from a supplying organisation logged into the API session, to be sent their chosen customer on squizz. These notices can advise how the goods are tracking through dispatch and delivery processes.
24
+
*/
25
+
class APIv1EndpointOrgSendDeliveryNoticeToCustomer
26
+
{
27
+
/**
28
+
* Calls the platform's API endpoint to push up a delivery notice and have it be sent to a connected customer organisation or person
29
+
* @param apiOrgSession existing organisation API session
30
+
* @param endpointTimeoutMilliseconds amount of milliseconds to wait after calling the the API before giving up, set a positive number
31
+
* @param customerOrgID unique ID of the customer organisation in the SQUIZZ.com platform
32
+
* @param supplierAccountCode code of the customer organisation's supplier account. Supplier account only needs to be set if the customer organisation has assigned multiple accounts to the supplier organisation logged into the API session (supplier org)
33
+
* @param useDeliveryNoticeExport if true then after the delivery notice is imported into Squizz it will be exported across to another system, using Customer Delivery Notice data export configured with the default data adaptor
34
+
* @param esDocumentDeliveryNotice Delivery Notice Ecommerce Standards Document that contains one or more delivery notice records
35
+
* @return response response from calling the API endpoint containing a Ecommerce Standards Document enclosed within it
0 commit comments