My Account
Actions & Action Templates
How to Change Your Commerce Type
Inviting New Users
Managing Notifications
Partnership Billing Settings
Passwordless Sign-in
Privacy Policy
Setting Billing Address
Signing Up
Single Sign-On (SSO)
Switching Between Accounts
Terms of Service
Viewing Subscription Info
Buyers
Automating Price List Creation via Actions
Buyer Product Validation Guide
Check Order Status
Downloading Assets
Inviting Sellers
Packing Slips - Buyers
Selecting Products
Seller SLAs
Shopify Product Syncing
Signing Up As A Buyer
Step by Step for Buyer Onboarding
Syncing Order Updates
Wholesale Guide for Buyers
Sellers
Onboarding
Adding Partners
Connecting Your Platform
Exclusive Collaborations - Syncing Unpublished Products
Fixing SKUs in Scientific Notation
How to Set Up Pricing
Marking Products as Active or Inactive
Seller Quickstart Guide
The 4Ps of Seller Onboarding
Resources
Adding Barcode Values in WooCommerce
Creating Product SKUs
Downloadable Image Links
Handling Returns
How Invoicing Works
Importing Products
Inviting Customers
Manual Fulfillment
Packing Slips - Sellers
Taxes and Manual Invoicing
Wholesale Guide for Sellers
Editing Price Lists
Sending Test Orders
Step by Step for Seller Onboarding
Integrations
WooCommerce
Shopify
EDI
Connecting through Seller EDI - Invoice (810) Specification
Connecting through Seller EDI for Dropship
Connecting through Seller EDI for Dropship - Advance Ship Notice (856) Specification
Connecting through Seller EDI for Dropship - Inventory Update (846) Specification
Connecting through Seller EDI for Dropship - Purchase Order (850) Specification
Connecting through Seller EDI for Dropship - Purchase Order Acknowledgements (855) Specification
Connecting through Seller EDI for Wholesale - Advance Ship Notice (856) Specification
Connecting through Seller EDI for Wholesale - Purchase Order (850) Specification
Webhooks
Building API Integrations
Connecting BigCommerce
Connecting Easypost
Connecting Magento 2 - Buyer
Connecting Magento 2 - Seller
Connecting through SFTP
Getting Started with the Buyer API
How Inventory Sync Works
Integrating your CRM
Supported Connection Methods
Updating Shipping Information
Security
Tutorials
Downloading EDI Files related to Purchase Orders
How To Update All Margins In A Price List
How can I confirm that Convictional can pull my Products from my WooCommerce Store?
How to Create a Test Order as an EDI Seller
How to Resend an Advance Ship Notice
How to Resolve " Your SFTP user requires delete permission on your SFTP server."
How to Resolve "Already Processed Files"
How to Resolve "Unable to access your SFTP server"
How to Resolve "Your SFTP user requires read permission on your SFTP server"
How to Resolve "Your SFTP user requires write permission on your SFTP server."
How to check if you are a buyer or seller on Convictional?
Migrating Ecommerce Platforms
Troubleshooting
- All Categories
-
- System Behavior Flags
System Behavior Flags
Updated
by Roger Kirkness
What are flags?
Convictional is designed to default to the right behavior for various B2B use cases. There are exceptions however where different companies handle a certain business rule in different ways, and there's no way to develop a universal design that serves everyone's needs. In those cases, we have flags that support can help you set on your account to change the behavior to suit your needs.
Using flags
In order to set a flag, please contact support@convictional.com. We plan on giving you the power to manage your own system behavior flags in future but we haven't added support just yet. We can activate or deactivate them. All of them are designed to be off by default, so when you create your account none will be active. Once we set them, it will remain on until you request it be turned off.
Available flags
We currently support the following flags, which may or may not be relevant to your use case:
Skip Buyer Notifications
In drop ship use cases, Convictional often syncs shipment updates from sellers into buyer systems. Buyer systems will often trigger notifications at that point to the end customer who ordered that shipment. The are valid use cases however where you would want to suppress these notifications, such as when the order is being bulked at a central facility before being sent to the customer. In those cases, the shipment details and tracking information are not accurate, and you can avoid that confusion on the part of the end customer by simply suppressing notifications from our side.
Ignore Inventory Type
Sellers have to decide, for the inventory in your system of record, whether to allow sales to continue to take place after you have run out of stock. We refer to this as the stock type, and every product variant has one. Sometimes a seller would want to run pre-orders and other order ahead scenarios on your core consumer ecommerce system, without providing the same access to your B2B channels. This is to avoid a bad experience on the part of an end customer who bought something from a third party seller on a B2B channel but had to wait an unexpectedly long time for the product to arrive. By setting ignore inventory type, we will always use the accurate stock for a product regardless of type.