This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
udropship:umarketplace:reference [2021/12/29 19:20] wtsergo |
udropship:umarketplace:reference [2021/12/29 21:17] (current) wtsergo [Vendor Statements Options] |
||
---|---|---|---|
Line 60: | Line 60: | ||
|Allow use of all PO udropship method associated system carriers | |Allow use of all PO udropship method associated system carriers | ||
|Allow use of all carrier methods when generate label|If No, then only shipping methods, which associated with dropshipping are allowed. If Yes then all shipping methods are allowed| | |Allow use of all carrier methods when generate label|If No, then only shipping methods, which associated with dropshipping are allowed. If Yes then all shipping methods are allowed| | ||
+ | |Explicitly visible in vendor portal system shipping methods|Specific system methods that will be visible in PO and Shipment forms in vendor portal. Could be used to create PO shipments with system shipping method distinct from PO method. Or add tracking number with method distinct from shipment method| | ||
|Allowed forced PO status change|AdvancedPO add-on required. If No, PO status can not change to shipped unless all PO shipments have status " | |Allowed forced PO status change|AdvancedPO add-on required. If No, PO status can not change to shipped unless all PO shipments have status " | ||
|Default custom text on the bottom of packing slip|The text defined in this field will appear in the bottom of the page on all packing slips| | |Default custom text on the bottom of packing slip|The text defined in this field will appear in the bottom of the page on all packing slips| | ||
+ | |Default display items number per page in vendor portal grids|Allows to change default value of items per page for vendor portal grids (POs, products, stock etc)| | ||
|Show totals in vendor portal order view|If Yes, statment total will be shown in order view in Vendor Portal| | |Show totals in vendor portal order view|If Yes, statment total will be shown in order view in Vendor Portal| | ||
Line 69: | Line 71: | ||
|Autoinvoice shipment|If Yes then shipment invoice will be created when shipment will reach a status defined in the next configuration. If " | |Autoinvoice shipment|If Yes then shipment invoice will be created when shipment will reach a status defined in the next configuration. If " | ||
|Auto-Invoice on these shipment statuses|Define shipment statuses corresponding to your workflow| | |Auto-Invoice on these shipment statuses|Define shipment statuses corresponding to your workflow| | ||
+ | |Cancel Order When All Vendors Canceled POs|Yes will try to automatically cancel PO when all vendors cancel their POs. Possible until order invoiced.| | ||
|Default Virtual PO Status|Default status for the orders containing virtual items only| | |Default Virtual PO Status|Default status for the orders containing virtual items only| | ||
|Default PO Status|Initially PO will have status defined here| | |Default PO Status|Initially PO will have status defined here| | ||
|PO Increment Type|If " | |PO Increment Type|If " | ||
|Shipment Increment Type|If " | |Shipment Increment Type|If " | ||
+ | |Increment Glue String|Can be used to setup different delimiter for PO/Shipment increment ids when they configured to be order based for PO and Order/PO based for shipments| | ||
|Attach PO Pdf to Vendor Notification|If Yes, PO PDF will be attached to Vendor Notification email| | |Attach PO Pdf to Vendor Notification|If Yes, PO PDF will be attached to Vendor Notification email| | ||
|New PO Vendor Notification Template|Transactional email to be used for PO Notification email| | |New PO Vendor Notification Template|Transactional email to be used for PO Notification email| | ||
Line 81: | Line 85: | ||
==== Vendor Statements Options ==== | ==== Vendor Statements Options ==== | ||
- | ^Vendor Statements Options >^For more information please follow this link http:// | + | ^Vendor Statements Options >^For more information please follow this [[http:// |
|Statement Email Sender|Select the email address from where the statment email will be send from| | |Statement Email Sender|Select the email address from where the statment email will be send from| | ||
|Statement Email Template|Transactional email to be used for sending statement emails | | |Statement Email Template|Transactional email to be used for sending statement emails | | ||
|Adjustment Comment Trigger Word|Use this as a first word in shipment comment for adjustment amounts in the following format: \\ ADJUSTMENT: -120 \\ Comment here \\ | \\ | |Adjustment Comment Trigger Word|Use this as a first word in shipment comment for adjustment amounts in the following format: \\ ADJUSTMENT: -120 \\ Comment here \\ | \\ | ||
+ | |Statement Usage|Check [[https:// | ||
|Default "Apply commission on Discount" | |Default "Apply commission on Discount" | ||
|Default "Apply commission on Tax" | |Default "Apply commission on Tax" | ||
+ | |Default "Apply commission on Shipping" | ||
|Default " | |Default " | ||
|Default "Tax In Payout" | |Default "Tax In Payout" | ||
|Default " | |Default " | ||
+ | |Default " | ||
|Default " | |Default " | ||
|Default Statement on following PO statuses|To setup required statuses to include in statements vendor orders that reach configured status (used if " | |Default Statement on following PO statuses|To setup required statuses to include in statements vendor orders that reach configured status (used if " | ||
Line 95: | Line 102: | ||
|Default " | |Default " | ||
|Enable Refunds|If Yes, the system will automatically try to determine refunded vendor PO items and reduce statement total accordingly| | |Enable Refunds|If Yes, the system will automatically try to determine refunded vendor PO items and reduce statement total accordingly| | ||
+ | |||
+ | ==== Payout Options ==== | ||
+ | |||
+ | |Predefined Payout Schedules|Allows to setup predefined schedules that could be used in //vendor edit > preferences > Payout > Payout Schedule//. This simplifies further vendor configuration for non-technical admin users| | ||
==== Customer Options ==== | ==== Customer Options ==== | ||
^Customer Options^ ^ | ^Customer Options^ ^ | ||
- | |Action on enable/ | + | |Action on enable/ |
|Action on delete vendor|Choose the correct option for vendor' | |Action on delete vendor|Choose the correct option for vendor' | ||
|Customer Notification on Shipment Completion|If Yes, shipping notification email will be sent to customer, when shipment status reaches Shipped| | |Customer Notification on Shipment Completion|If Yes, shipping notification email will be sent to customer, when shipment status reaches Shipped| | ||
+ | |Customer Notification on Delivered Shipment|If Yes, shipping notification email will be sent to customer, when shipment status reaches Delivered| | ||
|Customer Notification on Tracking ID|If Yes, then notification email with shipment and tracking info will be sent to a customer, when vendor adds tracking ID or generates shipping label| | |Customer Notification on Tracking ID|If Yes, then notification email with shipment and tracking info will be sent to a customer, when vendor adds tracking ID or generates shipping label| | ||
|Tracking ID Notification Template|Transactional email template used to send notification email (referred in " | |Tracking ID Notification Template|Transactional email template used to send notification email (referred in " | ||
Line 109: | Line 121: | ||
|Estimate Total Method|If "Sum of order vendor estimates", | |Estimate Total Method|If "Sum of order vendor estimates", | ||
|Estimate Error Action|If "Fail estimate & show error" and if no rates will be available from one of the vendors, then "No rates is available" | |Estimate Error Action|If "Fail estimate & show error" and if no rates will be available from one of the vendors, then "No rates is available" | ||
+ | |Enable Products Filter By Vendor Ship-To Location Limit|Unirgy_DropshipShippingClassLimit add-on functionality that allows filter products based on customer address according to vendor limitations settings| | ||
|Allow shipping extra charge|If Yes, then vendor can use extra shipping charges on checkout| | |Allow shipping extra charge|If Yes, then vendor can use extra shipping charges on checkout| | ||
|Use Custom HTML Customer Address Template For Vendors|If Yes, vendor can be configured to use the custom HTML template for customer address. Default | |Use Custom HTML Customer Address Template For Vendors|If Yes, vendor can be configured to use the custom HTML template for customer address. Default | ||
Line 119: | Line 132: | ||
^Product Stock Options^ ^ | ^Product Stock Options^ ^ | ||
- | |Vendor Decision Method|If " | + | |Vendor Decision Method|If " |
|Vendor Decision Method For Reassign|MultiVendor add-on is required. The configurations are the same as in Vendor Decision Method, however applies to the orders created from Admin area, when shipment' | |Vendor Decision Method For Reassign|MultiVendor add-on is required. The configurations are the same as in Vendor Decision Method, however applies to the orders created from Admin area, when shipment' | ||
|Hide vendors that failed stock check on admin area \\ Create PO page|AdvancedPo add-on is required, if Yes, then it will hide vendors that failed stock check on manual create PO page| | |Hide vendors that failed stock check on admin area \\ Create PO page|AdvancedPo add-on is required, if Yes, then it will hide vendors that failed stock check on manual create PO page| | ||
|Skip Stock Check For Reassign|AdvancedPo or MultiVendor add-on is required, if Yes then allow to select any vendor during shipment vendor reassign or manual created PO in AdvancedPO add-on. Stock check results is not taking into consideration | | |Skip Stock Check For Reassign|AdvancedPo or MultiVendor add-on is required, if Yes then allow to select any vendor during shipment vendor reassign or manual created PO in AdvancedPO add-on. Stock check results is not taking into consideration | | ||
+ | |Skip Limit Address Check For Reassign|Skip address limitations configured per vendor when doing PO reassign| | ||
|Skip Bundle "Ship Separately" | |Skip Bundle "Ship Separately" | ||
|Split Bundle by vendors|If Yes and bundle configured to ship separately and multiple vendors ship bundle simple products, it is possible to create separate cart items on checkout represent each separate vendor. This is a useful feature for SplitRate add-on users| | |Split Bundle by vendors|If Yes and bundle configured to ship separately and multiple vendors ship bundle simple products, it is possible to create separate cart items on checkout represent each separate vendor. This is a useful feature for SplitRate add-on users| | ||
Line 129: | Line 143: | ||
|Default status for product multivendor data|When new vendor starts to sell existing product, a line with the new offer is added in " | |Default status for product multivendor data|When new vendor starts to sell existing product, a line with the new offer is added in " | ||
|Hide out of stock vendors|Price comparison Add-on is required. If No, will show out of stock vendors in vendors offers table in product view page. If Yes, will hide them| | |Hide out of stock vendors|Price comparison Add-on is required. If No, will show out of stock vendors in vendors offers table in product view page. If Yes, will hide them| | ||
+ | |Show qty in order vendors reassign dropdowns|Yes - available qty will be added in reassign dropdown text| | ||
==== MicroSite Options ==== | ==== MicroSite Options ==== | ||
Line 134: | Line 149: | ||
^MicroSite Options > | ^MicroSite Options > | ||
|Enable " | |Enable " | ||
+ | |Allow per vendor sudomain level selection|Enable ability to setup vendor specific " | ||
|Subdomain level to use for vendor|Setting the level of the subdomain for vendor' | |Subdomain level to use for vendor|Setting the level of the subdomain for vendor' | ||
+ | |Use storecode before vendor key in URLs.|When "From URL path" is used in " | ||
|Landing page title|Title of the vendor' | |Landing page title|Title of the vendor' | ||
+ | |Landing page Meta Keywords|Meta Keywords to use in vendor microsite landing page| | ||
+ | |Landing page Meta Description|Same as above but for Meta Description| | ||
|Use this vendor as a template for new registrations|To eliminate repeating common vendors configurations, | |Use this vendor as a template for new registrations|To eliminate repeating common vendors configurations, | ||
+ | |Use vendor based product urls on landing page|Yes - all products urls will be based on vendor microsite url. No - will use global catalog urls| | ||
|Update Store Base URL|If Yes, all links on the vendor' | |Update Store Base URL|If Yes, all links on the vendor' | ||
|Automatically approve vendor applications|If No, all registrations need an approval by Admin \\ If Yes, all registrations will be automatically converted to vendor accounts with inactive status \\ If Yes and Activate, same as Yes, but vendors accounts will be active and ready to use| | |Automatically approve vendor applications|If No, all registrations need an approval by Admin \\ If Yes, all registrations will be automatically converted to vendor accounts with inactive status \\ If Yes and Activate, same as Yes, but vendors accounts will be active and ready to use| | ||
Line 151: | Line 171: | ||
|Product attributes to HIDE from vendors|Attributes selected here will not be visiable to the vendor| | |Product attributes to HIDE from vendors|Attributes selected here will not be visiable to the vendor| | ||
|Show all vendor products on frontend | |Show all vendor products on frontend | ||
+ | |Enable filter vendor categories on frontend|Yes - only vendor specific categories (if configured) will be used in the menu. No - global catalog categories as in default magento pages| | ||
==== Miscellaneous ==== | ==== Miscellaneous ==== | ||
Line 193: | Line 214: | ||
|Replace new line with custom char in fields during export|This supports only fields with simple format [var.name] (Magento CMS templating conventions < | |Replace new line with custom char in fields during export|This supports only fields with simple format [var.name] (Magento CMS templating conventions < | ||
|Custom templates for manual import|Create predefined templates, which can be used for manually created tracking or inventory batch import instead of one defined in vendor preferences| | |Custom templates for manual import|Create predefined templates, which can be used for manually created tracking or inventory batch import instead of one defined in vendor preferences| | ||
+ | |Custom templates for manual export|Similar to above but for export batches| | ||
+ | |Statement Export Template|Select one of the templates from above to use in ' | ||
==== Tier Commission ==== | ==== Tier Commission ==== |