udropship:umarketplace:reference
Table of Contents
uMarketplace Reference Guide
Global Configuration
Administrator Options
| Administrator Options > | System > Configurations > Drop Shipping |
|---|---|
| Vendor Comments Receiver | Vendor adds comments to shipments. Admin will receive notifications |
| Subscribe for extension update notifications | Update about the Umarketplace Versions |
| Use ShipService_v12.wsdl for fedex shipping labels | Set to Yes for the option to print labels for the SmartPost for FedEx users |
| Vendor Shipment Comments Email Subject | Admin will receive email with vendor's comments in shipment. Default text can be edited |
| Vendor Shipment Comments Template | Vendor's comments in shippments email template |
| Vendor PO Comments Email Subject | Subject of the vendor's PO comments email |
| Vendor PO Comments Template | AdvancedPO add-on required. Vendor's comments in PO email template |
| Letterhead Info | This letterhead will be available in every PDF statements |
| Letterhead Logo | Logo for the PDF statements |
| Letterhead Logo Aspect Ratio | Logo Ratio |
| Admin Interface Theme | Vendors can have its own theme. In case Microsite add-on will be used, Yes needs to be set in MicroSite Options > Enable “System View” menu item in vendor portal |
| Show vendor rates in “Shipping & Handling Information” box of order view page | It will show shipping rate breakdown by vendor in “Shipping & Handling Information” box of the order view page |
| Use “select … for update” to check if order already split to pos | Set to Yes in case Admin have duplicate PO's |
Vendor Options
| Vendor Options | |
|---|---|
| Local Vendor | List of Vendors from which Admin will choose the one to use as local. Local Vendor will be used if product/vendor is not defined. Site Owner should use Local Vendor to process its own warehouse orders |
| Make Available to Dropship on Order Status(es) | Orders Status(es) that will trigger Purchase Order creation |
| Change order status after POs beeing generated | Once Po is created, the order status can be changed to any options defined in this configuration. Custom order status can be created in System > Order Statuses > Create New Status |
| Strict mode of “Change order status after POs beeing generated” | Please refer to the Note bellow this configuration in Admin |
| Default Customer Shipment Status | Shipment Status, when created automatically |
| Make Order Ready to Ship on Printing Packing Slip | If Yes, then once Vendor is opened the Packaging Slip shipment status changes to Ready to Ship |
| Vendor Notification Email Recipient Field | Vendor Field, which contains email address to be used for Notification email |
| Vendor Notification Email Sender | From which email address Notification Email to be sent from |
| Default Vendor Notification Template | Transactional Email Template |
| Shipment Comment Vendor Notification Template | Transactional Email Template for Admin shippment comments |
| Default Vendor Password Reminder Template | Transactional Email Template for password reminder |
| Low stock vendor notification template | Transactional Email Template for low stock notification |
| Vendor SKU Product Attribute | Product attribute, which contains vendor's SKU to be used instead of Magento native SKU in vendor portal order view, packaging slip and vendor notification |
| Special Cost Product Attribute | Attribute which acts like Special Price for product's cost. To be used in case special sale dates are defined. For those who use cost product attribute to pay vendors |
| Font to use in PDF | Font to be used in packiging slip and AdvancedPO PDF. Using standard fonts will yield much smaller file size |
| Attach Packing Slip to Vendor Notification | If Yes, then PDF will be attached to the order notification email |
| Attach Shipping Label to Vendor Notification | If Yes, then shipping label will be attahced vendor notification email |
| Unique Email | If Yes, then each vendor should have its own unique email |
| Unique Vendor Name | If Yes, then each vendor should have its own unique name |
| Vendor Interface Theme | Vendor Portal Theme |
| Visible Preferences | Preferences, which can be modified by vendors in Vendor Portal |
| Allowed HTML Tags for Vendor Preferences | HTML Tags allowed in text area prefernces in Vendor Portal |
| Master Password | Setting Master Password for Administrator to access any vendor's account in Vendor Portal |
| Allow vendors to change shipment status manually | If Yes, then vendors are allowed to change shipment status manually |
| Attempt to void labels on deletion | if Yes, then labels will be marked Void upon deletion |
| Automatically complete vendor shipment | When tracking number is manually added by vendor and if No, then shipment status will not change, otherwise status will change to Shipped. If FedEx labels with poll tracking enabled and “At least one item shipped” is chosen, then shipment status will change to Shipped once one track is picked up. If “When all items are shipped” is chosen then shipment status will change to Shipped once all tracks are picked up |
| Available system shipping methods during vendor reassign in order | For MultiVendor Add-on, shipping method can be changed during order reassign |
| Allow WYSIWYG editor | If Yes, vendors allowed to use WYSIWYG editor in vendor prefences and in vendor's product modifications |
| Use autocomplete for vendor html select | If Yes, then the Text Box will appear in areas, where vendors are chosen. Text Box will allow to choose a specific vendor by typing the name of the vendor |
| Hide shipping amount in po pdf | If No, then shipping amount is visible |
| Hide shipping amount in packingslip | If No, then shipping amount is visible |
| Restrict shipment statuses in vendor interface | If No, there in no limit to shipping statuses to be changed by the vendor. If Yes, only limited shipping statuses will be available and can be chosen in “Available shipment statuses in vendor interface” |
| Restrict PO statuses in vendor interface | For AdvancedPo add-on. If No, there in no limit to PO statuses to be changed by the vendor. If Yes, only limited PO statuses will be available and can be chosen in “Available PO statuses in vendor interface” |
| Show product ID in “Manage Stock” in vendor interface | If Yes, then show product ID in “Manage Stock” in vendor interface |
| Always allow generate labels for these system carriers | Allowing generating shipping labels using chosen shipping carriers even if PO using a different shipping carrier |
| Allow use of all PO udropship method associated system carriers when generate label | When generating labels and If Yes, then system will allow to choose any system carrier from the shipping carriers associated with udropship method, used when order was placed |
| 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 “shipped” or “delivered”. If Yes, then PO statuses can changed |
| 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 |
Purchase Order Options
| Purchase Order Options > | AdvancedPO add-on is required for all the following configuration in Purchase Order Options |
|---|---|
| Autoinvoice shipment | If Yes then shipment invoice will be created when shipment will reach a status defined in the next configuration. If “Trigger whole order invoice” then invoice will be created for the whole order once one of the shipments will reach which configured in the next line |
| 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 PO Status | Initially PO will have status defined here |
| PO Increment Type | If “Magento Native”, PO ID will have a separate number. If “Order Based” PO increment ID will be determent by the following pattern <order increment id>-<PO ordinal number within order> |
| Shipment Increment Type | If “Magento Native”, shipment ID will have a separate number. If “Order Based”shipment increment ID will be determent by the following pattern <order increment id>-<shipment ordinal number within order>. If “PO Based” shipment increment ID will be determent by the following pattern <order increment id>-<PO ordinal number within order>-<shipment ordinal number within PO> |
| 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 |
| New PO Vendor Notification Template | Transactional email to be used for PO Notification email |
| PO Comment Vendor Notification Template | Transactional email to be used for PO commendnotification email |
| Allow change costs when manualy create po | If Yes, product custom cost can be defined when PO created manually |
| Default custom text on the bottom of purchase order PDF | The text defined in this field will appear in the bottom of the page on all PO PDF |
Vendor Statements Options
| Vendor Statements Options > | For more information please follow this link |
|---|---|
| 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 |
| 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 here for more details |
| Default “Apply commission on Discount” | If Yes, commission on discount can be applied and total will increase statement total by discount commission |
| Default “Apply commission on Tax” | If Yes, commission on tax (if include tax in payout) can be applied and total will be reduced by by tax commission. It is important to note that commission on price is calculated on price without tax. If commission on price including tax select needs to be calculated set that option to Yes and include tax in statement. |
| Default “Apply commission on Shipping” | it's similar to previous option, but will increase statement total by shipping amount commission. |
| Default “Discount In Payout” | If Include - reduce total by discount amount If Exclude but Show - discount amount will be shown in statement but not added to total payout If Exclude and Hide - won't be shown in statement and not affect total |
| Default “Tax In Payout” | If Include - vendor PO tax amount will be added to statement total If Exclude but Show - tax amount will be shown in statement but not added to total payout If Exclude and Hide - won't be shown in statement and not affect total |
| Default “Shipping In Payout” | If Include - vendor PO shipping amount will be added to statement total If Exclude but Show - shipping amount will be shown in statement but not added to total payout If Exclude and Hide - won't be shown in statement and not affect total |
| Default “Include shipping tax in shipping amount” | Control which total row to use to include shipping tax: tax line or shipping line. It doesn't effect total payout just for presentation purpose. |
| Default “Statement subtotal calculation based on” | If Price then price customer payed minus commissions configured plus transaction fee is paid If Cost, it will require to setup costs per product. Vendor cost minus commissions configured plus transaction fee is paid |
| Default Statement on following PO statuses | To setup required statuses to include in statements vendor orders that reach configured status (used if “Statement calculation based on”=PO) |
| Default “Statement calculation based on” | To control on which records to pay vendor there is global configuration. Select the one that fit your case or agreement with vendor |
| 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 |
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 | |
|---|---|
| Action on enable/disable vendor | If “Enable/Disable vendor product” then vendor product status will be synchronized with the vendor's status. If Enabled, then all products are enabled, if Disable then all products will be disabled. Have no effect when MultiVendor add-on used |
| Action on delete vendor | Choose the correct option for vendor's products, once vendor is deleted |
| 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 |
| Tracking ID Notification Template | Transactional email template used to send notification email (referred in “Customer Notification on Tracking ID”) to registered customers, if option Yes is chosen in “Customer Notification on Tracking ID” |
| Tracking ID Notification Template for Guests | Transactional email template used to send notification email (referred in “Customer Notification on Tracking ID”) to guests, if option Yes is chosen in “Customer Notification on Tracking ID” |
| Repeat tracking poll every … | How often poll tracking is run |
| Poll Tracking API | If Yes, the poll tracking will be turned On, if No, then Off |
| Estimate Total Method | If “Sum of order vendor estimates”, then on checkout, during shipping calculations, the shipping rates will be added based on vendor rates to produce the total shipping rates. If “Maximum of order vendors estimate ”, then the maximum amount will be used from all vendor rates |
| 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” will be displayed. If “Skip failed carrier call & show prices without” then vendors with not returned rates will be skipped in total shipping charges |
| 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 |
| Use Custom HTML Customer Address Template For Vendors | If Yes, vendor can be configured to use the custom HTML template for customer address. Default data can be copied from Configuration > Customer Configuration > Address Templates > HTML then modifications can be done in “HTML Customer Address Template For Vendors” |
| Use Custom PDF Customer Address Template For Vendors | If Yes, vendor can be configured to use the custom PDF template for customer address. Default data can be copied from Configuration > Customer Configuration > Address Templates > PDF then modifications can be done in “PDF Customer Address Template For Vendors” |
| Vendor Vacation Message | The message to be displayed on cart page next to the products, which vendor is on vacation |
Product Stock Options
| Product Stock Options | |
|---|---|
| Vendor Decision Method | If “Always use assigned vendor” only one vendor can be used to serve product and magento product stock is used to track this vendor's inventory “When in stock use local, otherwise use vendor” is a fallback method. Local vendor defined in global configuration: Configuration > Drop Shipping > Vendor Options > Local Vendor Magento stock managed for local vendor only. Local vendor can handle all products. Second vendor that can handle product defined in “Dropship vendor” product attribute, it's used only when local vendor does not have desired qty in stock. Non-local vendors that defined on product level is supposed to have unlimited stock (at least they treated so by udropship). It's not possible at that level to manage stock for non-local vendors (backup or fallback) because managento stock is already used to track local vendor inventory. MultiVendor add-on is required for “Multi Vendor: Least Packages + Lowest Cost” option will decide who will serve the product in cart based on (in priority order) the following rules: 1) stock availability 2) least packages produced 3) summary order cost (costs taken from vendor level) Multivendor add-on also adds ability to manage product stock separately for each vendor specified in “Dropship vendors” tab in product edit or “associated products” tab in vendor edit page “MSI: Least Packages + Source Priority” decision method appears when Unirgy_DropshipMsi module installed. This allows to utilize magento MSI Sources as vendor inventory warehouses. Similar to multivendor decision method but with MSI sources used in stock check and decision logic |
| 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's vendor is reassigned and in case AdvencedPO add-on is used, manually created PO's |
| 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 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 |
| 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 |
| Show vendor sku column in vendor portal stock section | If Yes, vendor SKU column will be visible |
| Stick microsite products in cart | Microsite add-on is required. If Yes and product added to cart from vendor's microsite, it will use that vendor regardless decision method If Yes & display vendor then same as Yes, in addition vendor's name will be displayed in cart item row If Yes (only when in stock) then same as Yes and vendor stock possess required quantity If Yes (only when in stock) & display vendor then the same as Yes, vendor stock possess required quantity, in addition vendor's name will be displayed in cart item row |
| 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 |
| Show qty in order vendors reassign dropdowns | Yes - available qty will be added in reassign dropdown text |
MicroSite Options
| 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 |
| 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 |
| 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 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 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 |
| 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 |
| Skip confirmation email | MicrositePro Version add-on is required. If No, upon approval vendor will receive email with the link to confirm his email address If Yes, no confirmation required. Vendor receives welcome email and his account ready to be used |
| Registration Confirmation Email Template | The template for the confirmation email sent to vendor upon completing the registration. Approval is pending by the Admin |
| New Vendor Confirmation Email Template | The template for the email sent to vendor with the link to confirm vendor's email address |
| New Vendor Reject Email Template | The template for the email sent to vendor upon rejection of the registration |
| New Vendor Welcome Email Template | The template for the email sent to vendor upon approval of the registration. The vendor's account is created and active |
| Carriers to allow during vendor registration | Carriers selected here, produce the list from which vendor can choose its own preferred carrier during the registration process |
| New Registrations Receiver(s) | Admin email addresses, who will be notified about the new vendor registration. Multiple email addresses should be separated by coma |
| New Registrations Email Subject | Subject of the new vendor registration email, which sent to the email addresses defined in New Registrations Receiver(s) |
| New Registrations Template | New vendor registration email template sent to the email addresses defined in New Registrations Receiver(s) |
| Staging Website | Website, which will be associated with products created by vendor from System View menu |
| 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 |
| 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 | |
|---|---|
| Email Transport | If site owner uses third-party to send emails in Magento and integration is not working with UDropship, the “Sendmail” option should be chosen to send emails |
Poll Tracking Error Notifications Options
| Poll Tracking Error Notifications Options | |
|---|---|
| Enabled | If Yes, the error notifications email will be sent to Admin |
| Sender (email from identity) | Email of the sender of the error notification email |
| Receiver (store owner) | Email of the receiver of the error notification email |
| Label Request Failed Email Subject | Subject of the email send if error occurred during the generating label process |
| Label Request Failed Email Template | Template of the email send if error occurred during the generating label process |
| Poll Tracking Failed Email Subject | Subject of the email send if error occurred during the poll tracking process |
| Poll Tracking Failed Email Template | Template of the email send if error occurred during the poll tracking process |
| Poll Tracking Limit | Number of attempts to retrieve poll tracking information |
| Poll Tracking Limit Exceeded Email Subject | Subject of the email send if number of attempts to retrieve poll tracking information is exceeded |
| Poll Tracking Limit Exceeded Email Template | Template of the email send if number of attempts to retrieve poll tracking information is exceeded |
Payout Paypal Options
| Payout Paypal Options> | Payout add-on is required |
|---|---|
| Test Mode | If Yes, testing mode for testing PayPal will be turned on |
| Use IPN to complete payout | If Yes, IPN verification is turned on. Siteowner's PayPal account IPN configuration section should have the following callback URL configured <magento base url>/index.php/udpayout/paypalipn |
| Account Email | Siteowner's PayPal account email address |
| Username | PayPal API username |
| Password | PayPal API password |
| Signature | PayPal API signature |
Orders Batch Options
| Orders Batch Options> | Batch add-on is required |
|---|---|
| Default Email Sender | Email address from which batch add-on order's exports will be sent if location configured as email address |
| Default Email Subject | The subject of the email from which batch add-on order's exports will be sent if location configured as email address |
| Default Export Orders Filename | Default name of the file to be used in case file name is not used in location |
| Export On Po Statuses | List of statuses, which PO have to reach in order to be ready to be exported |
| Save inventory import data in batch | Multivendor add-on is required if Yes, then import file data will be saved in the database |
| If import by vendor sku and it maps to multiple products | Multivendor add-on is required if Vendor's SKU in import file maps to multiple products choose the right action |
| Allow import new vendor/product association with inventory import | Multivendor add-on is required If import file contains references to products not associated with vendor if Yes, it will create new association if No, will skip the row |
| Replace new line with custom char in fields during export | This supports only fields with simple format [var.name] (Magento CMS templating conventions {{var var.name}} 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 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> | UMarketplace Extension |
|---|---|
| Parent category for tiered categories | Parent category created for tier commissions is selected here |
| Match Subcategories | if Yes, will search for match in subcategories recursively. If No, will look for exact assignment in one of tiered subcategories |
| Commission fallback lookup method | if Vendor First, per vendor settings will be looked first. If Tier First, tier settings will be used as main priority |
| Product attribute code for “Commission percent” | Code of the attribute which holds commission percent if specific per product |
| Product attribute code for “Tier Fixed Rate (per item)“ | Set per product fixed rate (instead of tier fixed rate) |
| Default Commission Percent | Set default commission percent for vendor who uses percentage set up |
| Tiered Rates | Define spesific tiers set up for each category |
| Fixed Rates Calculation Type | Set the transaction fee calculation process |
| Fixed Flat Rate (per po) [old transaction fee] | Set the amount, by which the statement total for each vendor PO will be reduced by |
| Rule for Fixed Rates | Set the rule (cart line property) by which proper fixed amount is determined. |
| Rule Based Fixed Rates | Fixed amount in table is defined depending on the rule value set in Rule for Fixed Rates |
Vendor Rating Options
| Vendor Rating Options> | VendorRating add-on is required |
|---|---|
| Allow customer review on the following statuses | Customer will be able to leave the review regarding shipping when shipping reaches the status(es) selected here |
| Delay in days to send “Email notification / Follow up emails” | Once shipment reaches status selected in “Allow customer review on the following statuses”, set the number of days on which to send shipments review reminder email to a customer. The days should be separated by comma, for example 3,5,7 If customer left the review, the notification will not be sent again |
| Customer Notification Template | Shipments review reminder email template |
udropship/umarketplace/reference.txt · by wtsergo
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
