Branch Profile Settings

The guide walks through the profile settings for each branch, and how you can configure your settings to streamline your purchasing process.

The Branch Profile is the control center for configuring the specific operational rules and workflows for a given branch or location within your organization. These settings are essential to managing how users interact with Tradogram, as they provide guardrails to ensure that your team is adding correct and accurate information when creating transactions and working within the system.

To access these settings:

  1. Go to the dropdown menu in the top-right corner and select Manage Branch.
  1. Click on Branch Profile in the left-hand panel.

‍

Branch Profile Information

Field Title Description
Name (required) Enter the name for your branch/location.
Phone Number Enter the contact number for your branch/location.
Default Currency All transactions will default to the branch currency unless it is changed manually or by supplier default.
Timezone The time zone set by your branch will affect the timestamped activity log, as well as the sending times for sealed requests.

‍

Transaction Settings

Field Title Description
Deliveries Enabled Choose whether to enable tracking deliveries in Tradogram. If this setting is turned off, users will not be able to add delivery notes to POs.
Expenses Enabled Choose whether to enable expenses as a transaction type.
Non-PO Invoices Enabled Choose whether to enable Non-PO Invoices. If this setting is turned off, users will not be able to add standalone invoices, and all invoices will require a PO.
Inventory Enabled Choose whether to enable inventory tracking. If this setting is turned off, items cannot be marked as stock items, and users will not be able to track the stock of items.
Allow External Items to be added Choose whether to allow users to add external items to transactions. If this setting is turned off, users will only be able to add database items to transactions.
Tax Option on Transaction Choose how taxes will apply to transactions. There are 2 options for this setting:
Taxes are applied on the transaction
Taxes are applied per-item

See more details on the different tax options here

‍

Checkbox Options

" field throughout Tradogram. Once activated, you must enter both the singular and plural custom terms (e.g., "Class" and "Classes" or "Budget Unit" and "Budget Units") into the provided text boxes. This feature ensures the system's terminology matches your company's existing financial and organizational language. Use a custom name for terms & conditions. Enabling this feature allows for the complete customization of the "Terms & Conditions" nomenclature via an open text field. The custom title entered will replace the default label across the entire Tradogram platform. This ensures the field title is consistent with your company's legal or contractual terminology, specifically changing the field title or the Purchase Order (PO) visible to suppliers and all internal users. Keep approval records if an exempted user edits the transaction. By default, any edit to a transaction resets all existing approvals. Enabling this setting creates an exception for users designated as "exempted" from specific approval rules. When an exempted user modifies a transaction, the system prevents the reset of the approval workflow, preserving any existing approvals already recorded. This allows authorized users to make necessary adjustments without restarting the entire approval process. Enable Ad-hoc approvals. Enabling this feature grants users the ability to manually add supplementary, one-off approvers to any transaction (e.g., PO, Requisition). These ad-hoc approvers are added dynamically and on a case-by-case basis, operating in addition to any existing, rule-based approval workflows already configured for the account. This provides necessary flexibility for exceptional circumstances. Enable unique item numbers. Enabling this critical setting enforces data integrity by requiring that every item saved to the database must possess a unique item number. If a user attempts to add a new item using an identifier that already exists in the system, the platform will prevent the item from being saved. This ensures there are no duplicate records and simplifies inventory management and system integration. Show transaction details in approval emails. Enabling this feature converts approval email notifications into actionable summaries. Instead of a basic link to the transaction, the email will include a full copy of the transaction details and provide the approver with direct "Approve" and "Reject" buttons within the email body. This dramatically accelerates the approval process by eliminating the need for the user to log into the platform to review and act on the request. Allow suppliers to terminate contracts. Enabling this setting grants suppliers the functionality to initiate the termination of a contract via the external portal. If the supplier formally terminates the agreement, the corresponding contract record within Tradogram will automatically be updated to the Terminated status. This ensures that your system accurately reflects the current, legally binding status of the agreement based on external supplier action. Make all Requests in sealed mode by default. Enabling this setting enforces a strict "Sealed Bid" environment for all new requests (RFQs). When active, the system defaults to sealed mode, meaning supplier pricing and bid details remain hidden from internal users until the specified bidding deadline is reached. Furthermore, users are prohibited from reverting the request to an open bid format. If disabled, users are restricted to using the pre-defined default email template, ensuring consistency in all outgoing supplier correspondence. Include Required Documents on requests. This setting extends the visibility of the "Required Documents" table to the initial Request stage (e.g., RFQ). When enabled, users can select and specify mandatory documents that must be included by the supplier when submitting a quote. If disabled, the ability to specify these required documents is limited only to the final Purchase Order (PO), removing this communication from the bidding process. Allow requisitions to be converted into expenses. Enabling this feature adds "Expense" as a valid outcome for a completed requisition. By default, requisitions can only be converted into a Purchase Order (PO), Request, or fulfilled from Inventory. When this setting is active, it allows a user to process a requisition directly as an expense record, accommodating internal requests for non-procurement costs (e.g., travel claims, subscriptions) within the standard workflow. Enable offer binding date on request offers. Enabling this setting introduces an optional "Binding Date" field for suppliers responding to a Request (RFQ/RFP). The date entered by the supplier acts as an explicit expiration date for their quoted pricing and terms. This provides procurement teams with a clear timeline for when the offer is financially valid. Make offer binding date mandatory. When the "Enable offer binding date on request offers" setting is active, enabling this option makes the Binding Date a mandatory field for suppliers responding to a Request (RFQ/RFP). The supplier cannot submit their quote until they have specified an expiration date for their pricing and terms. Create requests only from requisitions. Enabling this setting restricts the creation of all Requests (RFQs/RFPs) to strictly using items sourced from approved requisitions. Users are prevented from directly adding inventory items or external items when creating a new request. This ensures that every item put out for bid has first been internally requested, reviewed, and formally authorized through the requisition approval workflow. Hide Project Summary from Detailed Purchase Order PDF. This setting controls the visibility of internal cost allocation data on the external Purchase Order (PO) PDF. Enabling this option hides the "Project Summary" table from the detailed PO PDF; this table, by default, displays a breakdown of the total dollar value spent per project on that order. Disabling this setting ensures that your supplier does not see this internal project cost allocation data. Allow linking required documents to request compare options. Enabling this feature allows you to integrate mandatory document submission (the "Required Documents") directly into the formal Request Compare screen. This means that compliance checks, such as the submission of a Certificate of Insurance or a specific license, can be formally tracked and factored into the final decision alongside price and other comparison criteria when evaluating supplier offers.
Was this article helpful?