# September 15 - S\&S incoming shipments tab, Box scanning, bugfixes & Improvements

## :tada: New Features

### :truck: S\&S Incoming shipments tab

Now we have a new section in our app to display all the incoming shipments from S\&S. It's located under the Incoming tab in the receiving module where now we added nested tabs to display the normal incoming orders and a new tab for S\&S shipments. In this new view, user can filter by free text matching, order location, and expected delivery date. 

<figure><img src="/files/QFTa74YxA43wPSlB80KY" alt=""><figcaption></figcaption></figure>

### :package: Box scanning results in receiving orders pages

Since we deployed a new module in our CS-Platform app for box scanning/counting, we are displaying a visual to the user of that data in the corresponding receiving order page. We are also marking the receiving order as fully received or partially received based on the scanning/counting input coming from the CS-Platform new scanning/counting module.

<figure><img src="/files/MV2iYYHFqwBRWDpjUoiR" alt=""><figcaption></figcaption></figure>

{% embed url="<https://www.loom.com/share/ed15b9b0e3c545d7a4bdd1659743fb6a?sid=ff44b657-82fa-4801-a6e4-d7e22a277d20>" %}

## :lady\_beetle: Bugfixes

:heavy\_check\_mark: Fixed issue with order's defined charges when re-ordering. They were not being blanked and were carried over the new order.

## :rocket: Improvements

:heavy\_check\_mark: Implemented Quickbooks API's compliance according to Quickbooks API version 3.

:heavy\_check\_mark: All users can access to Work In Progress (WIP) dashboard now.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.culturestudio.com/release-notes/decorator-platform/september-15-s-and-s-incoming-shipments-tab-box-scanning-bugfixes-and-improvements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.