# Design considerations

Source: https://developer.avalara.com/avatax-dm-combined-erp/document-management/design-considerations/

# Design considerations

Whether you are a technology partner working to become certified or an API customer, this section describes how you should design your AvaTax application.

**Certification for technology partners:**

What should your integration's user interface look like? What design elements should you include? For partner certification, this section describes the design elements that are necessary in order to become certified. These UI elements have been carefully crafted to help you create an integration that is straightforward and uncomplicated for your users and to help ensure that your integration is tax compliant.

The badge requirements are broken down into the following types:

-   **Required**: This design element is required in order to become certified.
-   **Suggested**: This design element is not required, but we recommend that your UI includes suggested elements.
-   **Conditional**: Depending on your use case, this design element may be required.

**API customers:**

For API customers, following these badge certification requirements is not necessary; however we recommend that you follow these guidelines when using AvaTax APIs in your own systems.

[Previous](/avatax-dm-combined-erp/sales-tax-badge/refunds-faqs)

[Next](/avatax-dm-combined-erp/document-management/design-considerations/create-customer-record)