> For the complete documentation index, see [llms.txt](https://guia.fenicio.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guia.fenicio.help/integraciones-y-herramientas/erps-homologados/bricks-by-designware.md).

# Bricks by Designware

## Cobertura

* :flag\_uy: Uruguay

## Integración

Bricks es un sistema de gestión integrado que centraliza la operativa general de una organización.\
Cubre áreas como ventas, cobranzas, compras, pagos, stock, caja, bancos y contabilidad.

Cada operación actualiza automáticamente todos los módulos relacionados en tiempo real. Por ejemplo, una venta a crédito impacta de forma inmediata en deudores, stock, caja, documentos y contabilidad, todo desde una sola carga.

## Contacto comercial

🤵Ventas - <ventas@designware.com.uy> - 2613 8196 /  +598 91 506 124

## Más información

{% hint style="info" %}
Esta integración tiene costo de implementación.
{% endhint %}

[Sitio de Bricks by DesignWare](https://designware.com.uy/bricks/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guia.fenicio.help/integraciones-y-herramientas/erps-homologados/bricks-by-designware.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.