My issue is with limiting the code's use to specific customers. I tried changing the eligibility to specific customers I enter manually or to a customer segment I created. My issue is, in testing that code works for ALL customers. I went on a new device/browser and created a cart. That code works for anyone who has it.
It sounds like you've set up your discount code correctly. The Specific customers setting works based on the customer email, so only the email addresses listed should be able to use the discount code.
Sophia Social Care @ Shopify
- Was my reply helpful? Click Like to let me know!
- Was your question answered? Mark it as an Accepted Solution
- To learn more visit the Shopify Help Center or the Shopify Blog
When you enter the code at checkout, are you entering an email address? The code might appear to be working at first, but if you enter an email address that is not on the list of customers approved for that discount, a message should pop up at checkout letting you know that the code isn't valid.
The settings in my screenshot above will work for specific customers only. If you're noticing that your code works for any email address, please contact our team via the Shopify Help Center so we can investigate.
One of my clients works with influencers and gives them codes that people can use at checkout. These tend to be 5% off the whole order or 5 off the whole order. They also run their own special offers; for example, at the moment they are offering 30% off a new product.
Has this been solved yet? Such a major design flaw! Anyone with a sales funnel and multiple sources of traffic will have a nightmare with this. I emailed customer service but they always take a while to respond; curious if anyone else has figured out a way to turn off double discounts? This might be the final straw that makes us head to Shopify.
I've recently been forced to update my arlo app on my apple phone. When attempting to log on I would recieve an authentication code but did not know where to enter it. With the old app there would be a new to enter the code. After lots of digging I found somewhere it said to enter the code after my password. The problem now is apparently I've been locked out after too many tries. I'm recieving the code "Unused second factor auths limit reached". Any ideas of what I need to do? I'm paying monthly to see my cameras and I cannot log in. I tried logging in on desktop and resetting my password but that didn't help.
Hello James thank you for responding. I am now receiving authentication codes but I have another issue. Ever since being required to upgrade my mobile app the pop up screen to enter the code does not appear. I enter my log in info and it texts me a code but no place to enter it. The app just goes back to the home screen with the option to log in or create new account. I can access my cameras from my PC and my wifes phone but there seems to be an issue with my app. I tried deleting and re-installing many times. I'm running ios version 16.2 which I believe the app requires to be at least 11; so I'm currently confused on what to do.
For personalized support specific to the Arlo products you own, access Support from within the Arlo iOS or Android App. Simply login to your Arlo App, go to Settings, Support, then select the Arlo product you would like support for.
Edit: to be clear, we are using Twilio for phone message delivery, if that matters. Because we are in Canada, by default only Canada & the USA are enabled in our Twilio environment. If we want to send phone messages to phone numbers outside North America we need to enable those countries. To avoid confusing users we would like to limit the list of allowed countries in the enrolment flow to those countries we have enabled in Twilio.
Yes. Your company's Procore Administrator can limit the number of cost codes shown in the Timesheets tool's 'Cost Code' drop-down list. Limiting cost codes helps prevent miscoding or choosing a cost code that is not associated with labor hours. To learn how to limit the number of cost codes, see Configure Advanced Settings: Company Level Timesheets.
In the process of concatinating as mentioned above we are facing a challenge on the restriction on character limit of 60 on codes..Any suugestion on best possible way to address this issue would be of immense help
If you go with flat lists, which is typical for a data hub in Anaplan, you'll always need to load the parent in the system module. Just the parent. All the levels above parent can be calculated using formulas.
4. Note: SKU. This is my best practice but you may have your own. I always create a "reporting SKU Code" rather than using the EAN, UPC, or GTIN. The reason is because sometimes a new EAN has to be created for the same item to the customer. Even if there is a change to the SKU it's the same to the customer - plus you may want to replenish around the the reporting SKU not the individual EANs. I'll need a way to roll up those EANs to a reporting SKU. Trust me on this one, you'll thank me later!
Create your flat lists. the structured list is something that would reside in your spoke application. The data hub should only have flat lists. I'll show you why at the end when we build the structured lists.
Great overview. One thing I've noticed and had Anaplan come back to me on is the fact that if you're loading in a hierarchy, the codes of members between the hierarchy must still be unique or it'll throw an error.
In our scenario, we have a same color coming under two different Depts. i.e., color "Anaplan Way Blue" comes under Depts "Anaplan Way" and "DISCO" (might sound a little weird, but that's the way data is organized in this use case)
So, even though it is the same color, we are having to create two unique color codes in accordance with the Depts. Hence, we had to resort to concatenation of the parent and the level below it (eventually the codes spilling over 60 char).
In your case, then you would have to use a Numbered list with the concatenation of the codes, but that doesn't mean you have to use the concatenation on all levels. Your use case is not unique and in most cases, the bottom or last level is only repeated within the hierarchy. In this case, use concatenation of the codes at the bottom level. So, the first 3 levels would be a standard composite hierarchy and the last level would be a numbered list with the code being parent of the code_code of the member.
If that is the case, then concatenation is the only way to go. To get around the 60 character limit, have you thought about having an "Anaplan" code? This is how it would work...In your flat lists, you would have the real code from the source system. In the SYS Properties module for that list, you would have an "Anaplan" code to which you would use for the hierarchy code. For example, in your Product Category Flat list, say a members code is 1000000000009, but in Anaplan, the "Anaplan" code would be 10. The SKU flat list, a member from the source could be 20000009, but in Anaplan, the "Anaplan" code would be 20. So, in the Anaplan hierarchy, the code would be 10_20.
If you don't have a SKU code, then how are you going to get the transactional data into Anaplan? Where is the SKU data coming from, the actual source system with the transactional data? If it is like 99.99% of all source systems, they have a code. This might not be available to you right now, but IT will certainly have it. Ask them to redo exports to include that.
The Enforcement and Compliance History Online (ECHO) system provides a compendium of the effluent parametric limits that are identified in the NPDES permits issued to entities (municipal, federal, and commercial facilities) that discharge pollutants into the navigable waters of the United States. These limits identify what pollutants can be discharged and how much of each pollutant can be discharged as well as certain water conditions such as pH and dissolved oxygen content that must be maintained at the locations where the discharges occur. At EPA, the official source of NPDES limit data is stored in the Office of Enforcement Compliance Assurance, Integrated Compliance Information System (ICIS), where it is extracted by ECHO.
The national permit limit dataset is comprised of all permit limit information in ICIS-NPDES until the present day. The zip file contains one CSV file named NPDES_LIMITS.csv. Users also have the option of downloading permit data for a specific federal fiscal year and jurisdiction.
Note: When opening the file in Excel, values may display as dates due to the formatting (E.g., "01/30" describes monthly frequency sampling, but may display in Excel as "30-Jan".). Values should display correctly when opening as a text file.
LIMIT_SAMPLE_TYPE_CODE - The sampling method required by the permit to be used to provide values on the DMR for the limit. For a list of all codes and descriptions, download the Sample Type Reference Table (CSV) (1.7 K).
c80f0f1006