UnirgyWiki

User Tools

Site Tools

You are here: start » udropship » umarketplace » reference
Trace:
udropship:umarketplace:reference

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
udropship:umarketplace:reference [2021/12/29 20:56]
wtsergo [Product Stock Options] 		udropship:umarketplace:reference [2021/12/29 21:17] (current)
wtsergo [Vendor Statements Options]
Line 102: Line 102:
 |Default "Statement on following shipment statuses"|To setup required statuses to include in statements vendor orders that reach configured status  (used if "Statement calculation based on"=Shipment)| |Default "Statement on following shipment statuses"|To setup required statuses to include in statements vendor orders that reach configured status  (used if "Statement calculation based on"=Shipment)|
 |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 ====
Line 132: Line 136:
 |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" limitation|By default to allow bundle items to be shipped separately, all bundle specific options should be dynamic (Price, Weight, Ship Separately).  \\ This option skips that limitation and only "Ship Separately" considered. While using this option make sure the shipping calculation  methods does not rely on weight. Also, in some cases it could lead order/invoice totals to be calculated incorrectly. Use this option with caution | |Skip Bundle "Ship Separately" limitation|By default to allow bundle items to be shipped separately, all bundle specific options should be dynamic (Price, Weight, Ship Separately).  \\ This option skips that limitation and only "Ship Separately" considered. While using this option make sure the shipping calculation  methods does not rely on weight. Also, in some cases it could lead order/invoice totals to be calculated incorrectly. Use this option with caution |
 |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 138: 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 "dropship vendors" tab in product edit admin. \\ Status of the offer will depend on the selection| |Default status for product multivendor data|When new vendor starts to sell existing product, a line with the new offer is added in "dropship vendors" tab in product edit admin. \\ Status of the offer will depend on the selection|
 |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 143: Line 149:
 ^MicroSite Options >^Microsite add-on is required^ ^MicroSite Options >^Microsite add-on is required^
 |Enable "System View" menu item in vendor portal|If Yes, System View will be available in vendor portal for limited access to Magento admin area, where each vendor can modify its own products and create new products| |Enable "System View" menu item in vendor portal|If Yes, System View will be available in vendor portal for limited access to Magento admin area, where each vendor can modify its own products and create new products|
 +|Allow per vendor sudomain level selection|Enable ability to setup vendor specific "Subdomain level" version of global configuration. As result url structure may vary from vendor to vendor|
 |Subdomain level to use for vendor|Setting the level of the subdomain for vendor's landing page URL. Vendor  URL key, which can be set in Vendors Preferences, will be used as an unique variable to identify the vendor's landing page| |Subdomain level to use for vendor|Setting the level of the subdomain for vendor's landing page URL. Vendor  URL key, which can be set in Vendors Preferences, will be used as an unique variable to identify the vendor's landing page|
 +|Use storecode before vendor key in URLs.|When "From URL path" is used in "Subdomain level" setting and magento configured to use storecode in url this configuration allows to control which comes first storecode or vendor urlkey|
 |Landing page title|Title of the vendor's landing page. To insert vendor's name use [vendor_name]| |Landing page title|Title of the vendor's landing page. To insert vendor's name use [vendor_name]|
 +|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, admin can create vendor with basic configurations.  Selected, in this option, vendor's values will used as a template for a new registrations.| |Use this vendor as a template for new registrations|To eliminate repeating common vendors configurations, admin can create vendor with basic configurations.  Selected, in this option, vendor's values will used as a template for a new registrations.|
 +|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's landing page will be based on vendor landing page URL| |Update Store Base URL|If Yes, all links on the vendor's landing page will be based on vendor landing page URL|
 |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 160: 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  \\ (including multivendor associations) \\ |MultiVendor add-on is required. \\ If No, then vendor landing page will only display products, which associated using Dropship Vendor attribute \\ If  Yes, landing page will display products, which associated using Dropship Vendor attribute and with vendor offers in Dropship Vendor Tab  \\ in Product Edit| |Show all vendor products on frontend  \\ (including multivendor associations) \\ |MultiVendor add-on is required. \\ If No, then vendor landing page will only display products, which associated using Dropship Vendor attribute \\ If  Yes, landing page will display products, which associated using Dropship Vendor attribute and with vendor offers in Dropship Vendor Tab  \\ in Product Edit|
 +|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 202: 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 <nowiki>{{</nowiki>var var.name<nowiki>}}</nowiki> not supported)| |Replace new line with custom char in fields during export|This supports only fields with simple format [var.name] (Magento CMS templating conventions <nowiki>{{</nowiki>var var.name<nowiki>}}</nowiki> not supported)|
 |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 'Export Orders' POs grid massaction. Will render result file based on this template|
  
 ==== Tier Commission ==== ==== Tier Commission ====
udropship/umarketplace/reference.1640811361.txt.gz · by wtsergo

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki