> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/gumu-tm-for-sage-300c-shopify-integration/pre-requisites/sage-300c.md).

# Sage 300c

Setting up GUMU Extension for sage 300c integration

The Sage 300c Web API presents certain limitations, with few key endpoints missing, notably the capability to retrieve detailed Product Inventory quantities. Understanding this, the GUMU™ integration introduces a utility designed to bridge this data retrieval need, as the API does not offer a direct solution. The GUMU extension utility is tailored to seamlessly integrate updated inventory quantity information from Sage 300 to Shopify. Follow the steps below for a smooth setup on the Sage 300 server.

1\.  A GUMUExtension.zip file will be provided. Administrator must copy this file in following path on the Sage 300 workstation&#x20;

&#x20;      **C:\inetpub\wwwroot**

2\.  Open Internet Information Service (IIS) to initiate the configuration process.     Navigate to Application Pools and create a new Application Pool named **"GUMUExtension"** by right-clicking.

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

4\. Select The GUMUExtension App pool and click on Advanced settings.

&#x20;          Set Enable 32-bit Application to True\
&#x20;          Set Identity to ApplicationPoolIdentity

<figure><img src="/files/8YY4wnM5V9r5V6YyQlXS" alt=""><figcaption></figcaption></figure>

5. Expand the Sites folder.

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

6. Right Click on Default Website and choose Add Application option.

<figure><img src="/files/7dCOidlcOnTogAp7IKnZ" alt=""><figcaption></figcaption></figure>

7. Fill the options listed below.&#x20;

&#x20;      Alias: **GUMUExtension**

&#x20;      Application Pool : **GUMUExtension**&#x20;

&#x20;      Physical Path : **C:\inetpub\wwwroot\GUMUExtension**

<figure><img src="/files/16Z03MrbUwWFzIDHZ5Td" alt=""><figcaption></figcaption></figure>

8. Click Ok.
9. Navigate to below path on server.\
   **C:\inetpub\wwwroot\GUMUExtension** Under this folder find GUMUUtility application and run this application as administrator.
10. &#x20;Configure below details :\
    &#x20;**Sage 300 SQL Server Name :**\
    &#x20;**SQL User Name :**\
    &#x20;**SQL Password :**\
    &#x20;**Database :**

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

Once these details are entered, they are automatically encrypted and saved in the configuration file. It's important to note that these specifics are necessary for the extension to establish a connection with the **Sage 300 database** and retrieve updated product inventory quantities, especially considering that the Sage 300 Web API is not exposed for this purpose.

&#x20;


---

# 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 dynamically by asking a question.

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

```
GET https://docs.greytrix.com/gumu-tm-for-sage-300c-shopify-integration/pre-requisites/sage-300c.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
