# February 2nd - OCR Purchase Order Importer revamp & other improvements

## :rocket: Improvements

:heavy\_check\_mark:  Revamped the OCR Purchase Order Importer tool.

:heavy\_check\_mark:  Added "created by" filter in orders module list.

:heavy\_check\_mark:  Added "approved date" filter in orders module list.

:heavy\_check\_mark:  Users are now able to mark a product as supplied on OCR's preview step.

:heavy\_check\_mark:  Users are now able to change order's name on OCR's preview step.

:heavy\_check\_mark:  Users are now able to change design's name on OCR's preview step.

:heavy\_check\_mark:  Phone number is no longer a required field on editing a distribution address.

:heavy\_check\_mark:  Added Quickbooks bilateral sync on order details view.

:heavy\_check\_mark:  Estimate orders can be paid now.

:heavy\_check\_mark:  Now able to add, update, delete, download client document files from S3

## :lady\_beetle:Bugfixes

:heavy\_check\_mark:  Fixed issue: Quickbooks erroring on syncing due to manually overriding API files.

:heavy\_check\_mark:  Fixed issue: Style code missed in order lines product's title.

:heavy\_check\_mark:  Fixed issue: Tier pricing is not being used on adding/editing a universal product.

:heavy\_check\_mark:  Fixed issue: Existing purchase orders lines units were not being updated on editing/adding an order line using the new universal product editor.

:heavy\_check\_mark:  Fixed UX issue where ACH validation and Credit Card validation were bleeding into each other if user entered in both information in a single session


---

# 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/february-2nd-ocr-purchase-order-importer-revamp-and-other-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.
